Comparison of Java and .NET

The striking similarities between the two competing platforms leads many people to attempt a comparison of Java and .NET. The Java platform is older, dating from the mid-1990's. But in 2000, Microsoft introduced the .NET Framework, a new platform with a Java-like language (C#) and associated development tools.

As of 2007, the Java platform and the .NET framework have been competing vigorously on the desktop, but especially in the area of server technology. Many software developers (programmers) become expert on one or the other, but few have time to learn both. The schism of understanding the two platforms has been widened due to misinformation and disinformation, with a fair amount of zealotry on the part of each system's defenders.

From a historical viewpoint, the two systems may be seen as having different goals. A primary goal for Java was to enable a program to run on several different operating systems; this was accomplished by providing implementations of the Java virtual machine for all prevalent operating systems, including members of the Unix family, Linux, Mac OS X and most versions of Windows.

Microsoft has been widely criticized for only implementing its .NET runtime "only on Windows." Such criticism does not take into account that Windows is not a single operating system (at least not from the viewpoint of a programmer who must call routines in the operating system). Even before Windows Vista appeared in 2007, there were already approximately 35 versions of Windows, all with slightly different application programming interfaces (API's). The difficulty of developing software for these many different Windows systems had led to a situation called "DLL hell", where the wrong versions of dynamic link libraries (DLL's) were encountered by programs trying to run. Creating the .NET framework solved this huge problem for Microsoft by making all versions of Windows alike to programmers.

In fact, some .NET programs can run on non-Windows platforms. Miguel de Icaza (co-creator of GNOME) has created an open source implementation of the .NET framework for Unix-like operating systems; it runs on Mac OS X, Linux and Sun's Solaris). Called Mono, this independent implementation of a "common language runtime" is based on .NET's ECMA/ISO standards and is not under the jurisdiction or ownership of Microsoft. From the other side, Java implementations for various operating systems come from the same vendor and are much more comparable with each other both in terms of performance and various subtle behavior inside the libraries. On the contrary, Mono project, while providing .NET under Linux, is a completely different implementation so more issues can be expected when migrating. Java system library is quite large and unified over various platforms when .NET offers much smaller standard library with multiple extensions that may or may not be available under .NET.

The .NET framework and the Java platform have diverged in various other ways, including that .NET was designed to allow many different programming languages to use its runtime and libraries (whereas the Java platform was not used for multiple languages until very recently). There was no theoretical reason for Java being the only language that initially used the Java runtime. It was only since perhaps 2006, in response to Microsoft's multi-language .NET strategy, that Sun finally began a push to get additional languages "targeting" the Java runtime.

Platform comparison

• Java was the model for Microsoft when it created the C# programming language
• Java and C# code look very similar; it is fairly easy to switch between the two
• Java is cross-platform; .NET is cross-language:
  • Java provides freedom from all OS differences (with diligence), by making necessary cross-platform compromises; Java does not provide cross-language calling
  • .NET makes dozens of versions of Windows alike for programmers; it eliminates the "DLL hell" which formerly occurred when installing Windows applications
  • .NET libraries can be used by any of the .NET compiled languages (of which there are dozens); libraries can be written in any .NET language
• the two platforms compete fiercely in the world wide web
  • JSPs require Apache web servers (Linux or Unix); these are HTML interlaced with code, that when called are compiled to Java Servlets.
    • called "servlets" if all code
  • JSP's can utilize normal java code via a 'include'.
  • ASPs require Microsoft's IIS6 web server; these are HTML interlaced with code
    • called "web handlers" if all code
  • both Linux and Microsoft web servers use load-balancing across mirrored web farms to scale up
• so-called "dynamic" languages such as Ruby are seen by some as the next stage beyond Java and .NET
  • Both .NET and Java now run Python and Ruby through Jython, JRuby, IronPython and IronRuby.

Java VM Languages

Many different languages have been ported to run on top of the JVM with a wide variety of programming styles.

• Java
• Python, via Jython
• Ruby, via JRuby
• Scala, a high-level language with a highly sophisticated type system
• Groovy
• Clojure, a LISP-like language
• Rhino, an implementation of JavaScript

.NET Languages

A great number of languages have been ported to run on top of the .NET virtual machine.

Some of the well-known languages:

• C#
• VB.NET
• ASP.NET
• F#
• C++
• Python, via IronPython
• Ruby, via IronRuby
• IronLisp / IronScheme / L# are all LISP/Scheme implementations on the .NET platform
• JScript.NET implements JavaScript on .NET

See the List of languages using the .NET Framework for more details.