Charles, Actually you don't really include the price of the VM just like you don't include the price of the OS you're running when you run say Linux, Windows, Solaris or Mac OS X with native code. The VM is not included because it is the machine. In Java's case it may be a virtual machine but it still is the machine and in a way the OS or OS-like as it includes all of the interfaces to things like I/O, sockets, sound devices and such.
It's the price of VM technology. .NET will also give you the same overhead (give or take a few Megs). Some VMs are quite tight but that can be chalked up to their specialization (e.g. the extemely specialized Flash Player which can be considered a VM since it runs a language specialized to provide graphics manipulation). VM's for game emulation like Project64 for playing Nintendo 64 games on the PC take up several Megs as well. VMWare is here to stay and now being considered part of the "environment" now that Sun and Microsoft have made it ubiquitous. On Tue, 2004-06-08 at 13:18 -0700, Gerald Bauer wrote: > This is the first of a series of articles on how to > use the Thinlet GUI technology. The key benefit of the > Thinlet framework is the power and ease it gives for > developing rich user interfaces in a very small JAR > file. Only 38KB for the core Thinlet JAR file will > open up a new world for your applications and applets. Isn't that 38k + the size of the average Java install which comes in closer to 15 megs than, well, 38k? ;) -- - Charlie
