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 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.
Compile Time
by logicnazi on Wed 12th Jan 2005 03:51 UTC

In answer to your quesiton Kramii I am proposing a combination of 2 and 3. Instead of fully JIT the application each time cached code snippets would be used but it would still execute in a JIT/emulator style enviornment so that sensitive calls can be emulated for security and other reasons. Furthermore, I am suggessting that the compilation proccess be continous and in the background so that the proccessor is always sitting around optimizing applications, or at least whenever it gets a small improvement in optimizations.