Microsoft's“Java implementation” included, in addition to a JVM, a set of software development tools it created to assist ISVs in designing Java applications.
We should just quietly grow j++ share and assume that people will take more advantage of our classes without ever realizing they are building win32-only java apps.
As mentioned above, the exemplary distributed system 100 is based on the Java programming environment and thus makes use of the Java runtime system 216.
Microsoft's faster JVM lured Java developers into using Microsoft's developer tools, and Microsoft offered those tools deceptively, as we discuss below.
The District Court found that, not only were these tools incompatible with Sun's cross-platform aspirations for Java--no violation, to be sure-but Microsoft deceived Java developers regarding the Windows-specific nature of the tools.
The post-processing module 140 determines which captured data satisfies predefined rules, e.g., business rules, and records this data in a file 180, such as a Java Archive(JAR) file.
Since the Java API provides a single common API across all operating systems to which the Java runtime system 216 is ported, the programs running on top of a Java runtime system run in a platform-independent manner, regardless of the operating system or hardware configuration of the host platform.
Three months later,"Microsoft's Paul Maritz told a senior Intel executive that Intel's[adaptation of its multimedia software to comply with] Sun's Java standards was as inimical to Microsoft as Microsoft's support for non-Intel microprocessors would be to Intel.".
At an August 1995 meeting, Microsoft's Gates told Intel that its"cooperation with Sun and Netscape to develop a Java runtime environment… was one of the issues threatening to undermine cooperation between Intel and Microsoft.".
When specifically accused by a PC Week reporter of fragmenting Java standards so as to prevent cross-platform uses, Microsoft denied the accusation and indicated it was only"adding rich platform support" to what remained a crossplatform implementation.
Finally, other Microsoft documents confirm that Microsoft intended to deceive Java developers, and predicted that the effect of its actions would be to generate Windows-dependent Java applications that their developers believed would be cross-platform;
Microsoft documents confirm that Microsoft intended to deceive Java developers, and predicted that the effect of its actions would be to generate Windows-dependent Java applications that their developers believed would be cross-platform;
In May 1995, Netscape Corporation“agreed… to include a copy of Sun's Java runtime environment with every copy of Navigator[Netscape's web browser], and Navigator quickly became the principal vehicle by which Sun placed copies of its Java runtime environment on the PC systems of Windows users.”.
Fortunately for Sun, Netscape agreed in May 1995 to include a copy of Sun's Java runtime environment with every copy of Navigator, and Navigator quickly became the principal vehicle by which Sun placed copies of its Java runtime environment on the PC systems of Windows users.
The JVM developed by Microsoft allows Java applications to run faster on Windows than does Sun's JVM, Findings of Fact p 389, but a Java application designed to work with Microsoft's JVM does not work with Sun's JVM and vice versa.
In May 1995 Netscape agreed with Sun to distribute a copy of the Java runtime environment with every copy of Navigator, and“Navigator quickly became the principal vehicle by which Sun placed copies of its Java runtime environment on the PC systems of Windows users.”.
English
中文
عربى
Български
বাংলা
Český
Dansk
Deutsch
Ελληνικά
Español
Suomi
Français
עִברִית
हिंदी
Hrvatski
Magyar
Bahasa indonesia
Italiano
Қазақ
한국어
മലയാളം
मराठी
Bahasa malay
Nederlands
Norsk
Polski
Português
Română
Русский
Slovenský
Slovenski
Српски
Svenska
தமிழ்
తెలుగు
ไทย
Tagalog
Turkce
Українська
اردو
Tiếng việt