Jim--what you're suggesting is nearly impossible. There is no way that MSFT can make Java--the language--a Win 95/NT 4.0 only solution. The only way to do so would be for us to buy SUNW (yikes!).
We do not own the Java language spec, we've only licensed it (just as NSCP has--ask your lawyers if you can modify the Java spec without the approval of SUNW...if you can, you probably got a better deal than we did).
As far as the MSFT JVM is concerned, first of all, I am not a liberty to discuss how we're implementing it, and secondly, it doesn't matter. The JVM exists to run Java applets--how it does that is not relevant to users of Java applets. That's like asking what 11 herbs and spices are in the Colonel's secret recipe...don't know, don't care, here's my money, please feed me lunch.
Those who are *really* interested to know should forward a resume :-)
The important thing is: IN NO WAY DOES THIS MAKE JAVA A WIN 95/NT 4.0 ONLY SOLUTION. As I explained above, a JVM allows you to run Java code on a particular platform--MSFT is implementing the *reference edition* for Windows, but SUNW is supplying the JVM for Mac and Unix. So developers will write their code with Java, compile it on the server side, and Java will run without change on all three platforms.
Keep in mind that the JVM spec is widely available to the public (I bought a $30 book and it came in the appendix!), and you can bet that other vendors will implement their own version if they don't like ours (pick up Andrew Schulman's book for another $50 or so, and you can make whatever "proprietary" API calls you want).
Or did I miss your point?
Bulls Won!! (Congrats to Sonics on a great season and series though)
DISCLOSURE: I am a Microsoft employee, but my comments only represent my own thoughts and opinions and in no way reflect a position, endorsement, or recommendation by Microsoft, it's officers, representatives, or associates. |
