Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Microsoft - The Evil empire -- Ignore unavailable to you. Want to Upgrade?

To: Kal who wrote (89)	10/28/1997 12:59:00 PM
From: Steve Booth	Respond to of 1600

Kal, Thanks for the URL. I couldn't remember where I read the information. I KNOW that the changes I was referring to did NOT deal with the COM/DCOM/CORBA issue. Interesting how the other points regarding Licensing Issues got ignored, eh? Here's the text that I was referring to: --- Beginning of Quoted Material: Sun: Microsoft added methods and fields to Java classes Since the final version of IE 4.0 was made available last week, Sun claims it has run the product through Java compatibility tests and has previously said that some changes to the API (application programming interface) could violate license agreements. Today, Sun announced that Microsoft has failed those compatibility tests of its IE 4.0 browser and Software Development Kit for Java. The company claims that Microsoft has added methods and fields to the Java classes on the Java hierarchy. According to Sun, approximately 50 methods and 50 fields have been added to the Java APIs within things like the AWT (abstract windowing toolkit) package and I/O package. Baratz says that, for example, the interface method used to query and find what color is painted on a computer's screen has been altered by Microsoft. According to him, in some cases "you have to use the extended version of the interface [provided by Microsoft] to get the answer." This means that applications would run differently on IE 4.0 than from a browser that fully supported JDK 1.1. --- End of Quoted Material