Force Microsoft to Carry Java?
torre writes "Well, there at it again. Sun has now begun its private litigation against Microsoft charging some pretty serious stuff. As we all know it has been widely reported that Sun looks to seek to force Microsoft bundle its java plug-in with their OS.
For a quick recap Sun sued Microsoft to stop shipping java since they had violated their licensing agreement. Sun won, got some money, and Microsoft got upto 7 years to continue shipping their outdated version. Microsoft recently decided that in XP they shouldn't ship their mangled version of java and Sun cried fowl demanding that they ship their plugin.
Now, what hasn't been reported in detail is the allegations that Sun has charged against Microsoft. In brief, they charge that
1) Microsoft has a monopoly in the OS, Web browser, and Office productivity markets
2) Is engaged in illegally tying
a. IE to windows3) Entering into illegal exclusive deals
b. Their workgroup software to their OS
c. IIS to their workgroup server
d. .net to their OS's
e. Active directory to both OS and workgroup OS and to Exchange
f. Exchange server to Office
4) Unreasonably restrained trade
5) Infringement on copyright
6) Engaged in unfair competition
In their settlement they look for and I'll quote "
Preliminary injunctions prior to trial requiring Microsoft to:
Distribute Sun's current, binary implementation of Java Plug-in as part of Windows XP and Internet Explorer.The preliminary injunction hearing is scheduled for December 3 - 5, 2002 at the U.S. District Court for the District of Maryland in Baltimore, Maryland. Permanent injunction requiring Microsoft to:
Stop the unlicensed distribution of Microsoft's Virtual Machine Java through separate web downloads, instead of incorporating within Windows XP and Internet Explorer, in accordance with Jan. 23, 2001 settlement agreement.
Distribute Sun's current Java Plug-InAll of this claiming that they've harmed java, the Java programming community and intimately Sun's shareholders. Now as the court battle begins its seems that sun has to prove that they are not looking unfair advantage. This seems to be a big issue as it would seem that they could achieve the same level of distribution by merely dropping four million with OEMs..."
Stop unlicensed distribution of Sun's Java code
Disclose and license proprietary interfaces, protocols and formats.
Unbundle tied products like Internet Explorer, IIS, Active Directory, Exchange, Windows server and .NET framework"
Microsoft's Java implementation was the best java implementation at it time. Microsoft had the fastest java implementation and much more stable than Nestscape's version (the other java version I had developed for).
.net and compared to java it really looks very appealing. I hope Sun doesn't succeed in stopping Microsoft from shipping the .Net runtime along with its OSs.
In addtion before JBuilder, VJ++ was the best java development envoirnment. Symantec's Visual Cafe totally sucked in comparison.
After Sun got Microsoft to stop shipping Java our client decided to scarp the java project we were working on.
I wish Sun had never sued Microsoft in the first place. Microsoft would have had to forever ship java. So what if they Microsoft added some extensions like delegates and support for activex. The added funtionality was really an advantage. Sun should have assimlated these extentions into the Java standard. Instead java has not had any major language enchancements in the past 10 years. We are currently exploring
Last I looked, Sun's J2SE runtime is free to distribute with your software in binary form, provided due credit is given, it is unmodified, and any extensions are clearly identified as such. Mobile JVMs, enterprise features and such are of course another matter.
...when you're writing a game...tweak the difficulty of "Easy" to something [your mother] can cope with. -- onion2k
The MS JVM wasn't compliant. It didn't include RMI or JNI, rather it had MS-developed, Windows-specific, incompatible versions of same. They also added JavaDoc doclets that actually had an effect on compiled code, therefore producing class files that were incompatible with compliant JVMs and in contravention of the JLS.
Sun's position was that under the terms of their agreement, MS should ship a compliant JVM (including RMI and JNI) or terminate the agreement.