Guys, this isn't about Microsoft or Sun forcing developers to use a particular applications platform, it's about users supposedly not gravitating toward java applets and applications because it is too difficult to run the JVM on Windows.
Sun's argument is that because Microsoft doesn't include the latest JVM with Windows, applications developers are reluctant to write java applications since it would require the users to download and install the JVM to run the applications.
This is a completely bogus argument for several reasons.
First, when the latest/greatest version of the JVM was installed on Windows, people STILL didn't write java applications because java was far too slow and had a horrible user experience. This fact alone makes it quite unlikely that developers are dying to write java client applications today and the only thing that stops them is the JVM availability.
Second, the entire idea that it's too hard for users to download and install the JVM, and this is why java isn't succeeding on the client side, is silly. Visual Basic flourished since version 5.0 because developers created applications people wanted, and either deployed vbrunXX.dll with their application, or users went and downloaded it themselves. Microsoft including vbrunXX.dll in their VB applications (where were few and far between), and didn't include it in the OS for a very long time (Win 98?), but it flourished. The same goes for MFC. It was the applications that drove adoption of the runtime, not the runtime that drove adoption of the applications.
Third, I would say that EASILY 95% of all Java development today is on the server, and J2EE development is still (although not for long, imho) the number 1 server applications standard. People simply don't write java client applications anymore. The web is almost always a better and even more ubiquitous platform for applications delivery. Even .NET developers, who have a seriously awesome WinForms library at their disposal, are by far more interested in ASP.NET and web applications development.
Lastly, I question the validity of the claim that java has been hurt in anyway by Microsoft's monopoly over the OS. Again, it was NOT because of Microsoft that people didn't write java client apps during the years that the JVM was up to date on Windows. It was because java sucked for client apps. In order to justify forcing Microsoft to include java in Windows, you must prove to me that it was Microsoft's OS monopoly that caused java client apps to fail. I see no evidence of this.
Certainly, Microsoft's OS monopoly now allows them to choose not to include java in Windows by default, but this has little affect on java because, as I said, few companies are developing client apps for java, and the injunction therefore does little to change java's status among developers.
|