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.
kernel a bad idea?
by mattb on Mon 10th Jan 2005 19:00 UTC

just an ignorant java developer who has an idea of whats being talked about, but self-taught/hobby level

i would like to say this is one of the most interesting articles ive read here in awhile. Managed languages are definately the way of the future. But if they are destined to become such an intregal part of operating systems of the future, wouldnt it make more sense to put the low level stuff into the kernel? wouldnt that allow for stuff like load handling and process optimization? maybe even a sandbox for the sandbox, have a generic, vm independant layer that would allow the kernel to know more about whats going on with the vm. i would think that the fewer levels of abstraction between the vm and the cpu, the better. would you mind explaining why it would be a bad idea?

one of the big problems with java at any rate, is that although platform independant sounds real nice, you still have platform dependant bugs, and platform dependant optimization. profiling a java app on windows can give wildly different results as on linux. and if we take cross-platform benefits off the table for a sec, dont we just end up with a slower implementation of the kernel?