To: Dale J. who wrote (11827 ) 11/19/1998 5:00:00 PM From: Kenneth E. Phillipps Respond to of 64865
Article in Internet Week re Microsoft compliance plansinternetwk.com Thursday, November 19, 1998, 11:00 a.m. ET. Microsoft Tools Team to Sun: No Problem By RICHARD KARPINSKI Calling this week's preliminary injunction much narrower than expected, a Microsoft developer tools manager today said the vendor would tweak its Java tools to meet the order but leave in all the platform technologies it believes Windows developers want. "Our initial concerns about this ruling were a bit exaggerated," said Tom Button, Microsoft's director of product management, developer tool. "The ruling is relatively narrow, and the changes the judge is requiring of us are relatively narrow." While Button officially represents Microsoft's tools group, he said the company also planned to support the changes requested by the judge to Internet Explorer and the Windows OS. While the statements are no doubt designed at least in part to downplay Sun Microsystems' major court victory, they nonetheless offer the first word from Microsoft officials that they plan to meet the demands of Sun. Following the court ruling, speculation has run rampant that Microsoft could be considering other solutions, such as using its own so-called "clean-room" implementation of Java, or dropping Java altogether. While Button would not comment on such speculation, he did say that "at this point it is so premature for anyone to think that was merited. As long as we have the ability to innovate and add value, we've heard nothing new to change our business or product strategies" in regard to Java. "We have no plans to ship an alternate framework," he continued, adding that "at this point, we're not ready to many any announcements not required in the order." Specifically, Button said the vendor would alter Visual J++ to enable several of its extension to the language--including Windows platform-specific keywords and compiler directives--as an option rather than a default within the tool. Developers would have to "flick a switch" to enable these non-Java-compatible elements, and, as per the court order, first see a dialog box warning them that they were entering a mode that would create Windows-specific Java code, Button said. He said Microsoft had no problem alerting users to that fact. Indeed, it was the message they had been stressing all along regarding Java. "We believe developers using Visual J++ use it primarily to build Windows software," he said. Button said Microsoft would also, per the court order, include Sun's Java Native Interface (JNI) in its runtime environments, as well as offer support for building code based on JNI in its Java tools. Up to now, Microsoft has only included is own native interfaces to the Windows platform, including Raw Native Interface (RNI) and J/Direct. That caused cross-platform problems for Java developers, because Microsoft's Virtual Machine is the only one to support those interfaces to Windows-native code. Every other VM relies on JNI.