It can do things (as the author of the article you linked to pointed out) which would be harder or impossible in real world hardware.

Never impossible. Even the software VM eventually goes down to hardware CPU(s). But it is true that the designer of instruction sets for a software VM usually won't bother to ask how easy a given instruction could be implemented in hardware. Often, they may not even have the know-how to figure out how to design a hardware-based architecture (which is fine, since their aim is software).

Some might be interested in an old architecture, the Burroughs B5000 (poke around Google for information), which was supposedly optimized to run higher-level languages. In the recent ACM interview with Alan Kay, he mentioned a benchmark on that machine (made in 1979) and a more modern one. The modern machine ran it 50 times faster. However, Moore's "Law" should have given it roughly 50,000 times speed up. Somewhere along the way, we lost around three orders of magnitude in speed due to bad architectures.

"There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.

In reply to Re^2: Parrot on a chip by hardburn
in thread Parrot on a chip by szabgab

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.