Linked by Peter Gerdes on Mon 10th Jan 2005 17:35 UTC
Editorial As a recent ACM Queue article observes the evolution of computer language is toward later and later binding and evaluation. So while one might quibble about the virtues of Java or the CLI (also known as microsoft.net) it seems inevitable that more and more software will be written for or at least compiled to virtual machines. While this trend has many virtues, not the least of which is compatibility, current implementations have several drawbacks. However, by cleverly incorporating these features into the OS, or at least including support for them, we can overcome these limitations and in some cases even turn them into strengths.
Permalink for comment
To read all comments associated with this story, please click here.
JIT is *not* faster
by mikeyd on Tue 11th Jan 2005 12:18 UTC

There is no way JIT can ever be faster, because whatever you do it's all opcodes in the end - and with the JIT you have the overhead of doing the compiling at runtime. It's revealing that I have yet to see a major java app without a splash screen, and ime performance when running is also far lower, at least in a GUI. Anyway, while it's true that JIT code running on an Athlon can be faster than arch=i386 compiled code on the same machine, natively compiled code for your machine will always be faster than JIT.