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.
cachign is good
by Yamin on Mon 10th Jan 2005 19:08 UTC

I think in general the idea is there. Cache native code is the major easily doable part.

I wouldn't be so eager to jump in and try to force VM (java...) to be regular applications though. To a certain extent, we 'trust' our OS, our hardware to be perfect while programming. In a similar sense, you should eventually be able to 'trust' your JVM. Things like memory protection...aren't really relevent in a VM like java.

You don't have random access to memory, so what is there to protect? Why bother with a context switch between java applications? Also additonal VM extensions to security...

Now, moving some JVM stuff into the OS also makes some sense. But now you lose some of the isolation between the OS and the VM.