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.
@logicnazi
by Deletomn on Tue 11th Jan 2005 11:47 UTC

Overall I thought your article was interesting. However, I believe you missed what I consider the most important point in joining the VM with the OS: True plug-and-play for hardware.

Let me explain: If a standard was developed for devices through which they could store their own device drivers and they could be easily retrieved (via the standard) by the OS, then you could simply plug the device into the computer and the OS would "instantly" understand how to use the device. The drivers would also be "crossplatform", so if say Linux distributions and the Mac OS implemented the VM, then the device would automatically work with those OSs.

I haven't done much hardware design work, so I don't really know how much this would add to the cost, complexity, etc. of the devices, but I feel that it wouldn't be too hard to add and I also feel it would be well worth the effort.