>It becomes platform specific because it no longer targets the Java Virtual Machine (JVM). Java apps (or applets) running realtime (sort of like running a VFP someprog.app using the VFP developer) on a JVM are the slowest. The java script is read and run line by line. Looping, as you might suspect, compiles each line (in real time) of the loop as it is encountered, over and over. Javac helps this somewhat. But taking the package to an exe or ELF binary with 3rd party tools creates platform dependent binaries that are also the fastest.
>
>One still has the source, which is platform independent, as long as software company doesn't extend a Java API into its own propriatary territory, thereby ending cross platform compatibility. (The only companies that do that sort of thing are the one trying to force the market using their monopoly advantage in what ever technology domian they may have a patent or trademark. This is why I prefer Open Source software, ie, GPL.)

Now this makes Java interesting! It also eliminates the need to even have a JVM on the target computer. So, if I were to make a Java app that I know will be run on Windows 95 computers only, I could compile it and run it off a freshly installed Win95 computer?

Thanks for the info! :)