J2EE vs. .NET in Productivity Comparison?

Matt Hughes asks: "When does one programmer's preferences (Java over Microsoft-anything because they hate Microsoft, or Microsoft over open-source because open-source is evil) and the variety of choices start to erode productivity? As a J2EE developer for the past few years, I admit that I've become frustrated at the number of choices out there. Every one offers a different way of doing things but they don't all interoperate (JBuilder doesn't natively understand Struts) and none of them -- in my experience -- pulls all of the web technologies together very succinctly. Does Visual Studio .NET and the .NET framework pull this together better than the open-source projects out there, or is it just as complicated in your experience? Is .NET too immature to be trusted? What are your thoughts?" For those interested in the raw performance numbers, Slashdot did a performance comparison between the two technologies, in an earlier article.

"I've recently been asked to produce a report listing the pros and cons of J2EE and .NET as a web application development platform. I've been using J2EE for years now and haven't even touched .Net as I dislike most Microsoft products. However, for the report, I am trying to be objective. From my own experience and from what I've read, it seems the defining issue for some people is choice.

As far as language preference, some argue Microsoft allows too much (VB.NET, C#, and supposedly everything else *eventually*) and J2EE too little (Java). As far as development environments, Microsoft offers too little (Visual Studio .Net, Windows Server 2003, Windows only) and J2EE provides too much (JBuilder, Eclipse, Tomcat, JBoss, Websphere, any OS/hardware combo, etc)."

Comments

Looking for Trolls?

[ClosedSource]

Believe it or not some people use Java for reasons other than hating MS. Some people use MS for reasons other than disliking open source.

Having said that, I do note that you are perpetuating the myth that Java runs on "any OS/hardware combo". This is untrue of any language but I suspect "C" comes closer to achieving it than Java.

Re:Looking for Trolls?

[scrytch]

Having said that, I do note that you are perpetuating the myth that Java runs on "any OS/hardware combo". This is untrue of any language but I suspect "C" comes closer to achieving it than Java.

I suspect you'll have a hard time running compiled C on any platform for which there is a compiler. Or for that matter, even build it unmodified without the benefit of autoconf unless it's among the most trivial of programs.

Not that Java has a lock on portability -- Perl and Python do just fine in that area too.

Re:.NET vs Java

[UPi]

Please note that the question wasn't C# vs Java, but .NET vs J2EE. The languages themselves are just plain irrelevant in this case. Also note that .NET is not just C#, but a whole bunch of CLI'ed languages (there's even a bastardization of C++ there).

I have used both J2EE and .NET, and there are a few things I can offer for the report.

• J2EE is more mature. It's been around longer, so it simply had a longer time to grow out of childhood sicknesses. For example: The documentation is more complete. .NET's docs are like all Microsoft docs: mostly generated, and sometimes the very reason you're reading them is missing. For example sometimes you don't have a clue what exceptions a library method can throw...
  
• .NET is pretty handy for what it was concieved: creating simple web-based DB frontends. If you want an object model behind it, with good persistency options, you will want to choose J2EE instead with it's Enterprise Java Beans.
  
  This is quite general for everything: e.g. .NET has the almighty DataSet, J2EE has persistent beans. DataSets are simple, but go back to the structured programming age. The beans are more sophisticated, but take a little longer to get the hang of.
  
• Learning curve: IMHO J2EE takes a little longer to comprehend. Once you got the hang of them, though, both environments are easy to use.
• Oh and one more thing: C# doesn't check the exceptions. I may be a purist, but I just detest that. You have to document, maintain, and generally keep an eye out for your and the system's exceptions all the time (of course sometimes you have no idea what system exceptions there are..)
  

Summary: If you want a quick and dirty DB frontend, go for .NET (with C# or VB). If you want something more complex, I'd recommend J2EE.

Re:.NET vs Java

[Khazunga]

I also like the fact that I can code in C#, Smalltalk, Eiffel, ilasm (yeah right;)) or some other language, and if a Visual Basic programmer want to use my classes (s)he can just use them, like they were native classes.. No modifications needed. No wrappers needed.

The multi-language aspect of .NET, much hyped by MS-marketing, is a common characteristic to all bytecode-interpreted languages. Java has its own list of bytecode compilers: 165 of them, by current counts.

Objective .NET/C# vs J2EE/Java Comparison

[massive-cow]

I have used both a fair amount. My previous job was writing Java business web applications, and I am currently managing the development of a C# webservice (for the server) and a C# winforms client.

Let's start with the picture from 10,000 feet: C# is aimed squarely at Java, and for all intents and purposes, it is a superset of Java. Similarly for .NET and J2EE, though they are less similar than the language comparison.

Language Differences:

C# has less integrated threading support. (which is a bad thing, imho)

C#'s XML and SOAP integration make it /ideal/ for any application dealing heavily with either protocol. In fact, I would say that it is nothing short of brilliant.

Java's XML integration is a nightmare. JAXB is the only thing that comes close to being halfway decent, and it still doesn't come close to the integration C#. XML serialisation in C# is fast and beautiful.

C# gives you far more control over the dynamic reloading of classes, as well as increased security through what .NET calls 'AppDomains'. This is a very powerful feature.

C# documentation isn't quite as nice or refined as the standard javadoc fare, but MSDN is a pretty nice source, though sometimes you have to look a little harder or deeper than you would with the javadocs.

In general, both APIs are very clean.

As for maturity, I don't really think that's an argument. Most of the Java technologies available now (especially the XML/web services bits, in which the competetition is most fierce) are no older than .NET/C#.

I think the larger question is the underlying /platform/ maturity, but I will leave the zealots to argue Windows vs Unix.

Do you feel comfortable locked into a Microsoft platform and x86 hardware? Personally, for a server, I don't. Go help out Mono, which is progressing nicely, but could definitely use some more help. (http://go-mono.org)

If you do, I would definitely go with .NET and C#. When Mono gets further along for web services, it will certainly be a force to reckoned with. As for writing webservice and database clients for Win32, it is really quite nice. You could use GTK# and have it cross-platform, yet still take advantage of features that C# includes.

In short, the pros: excellent XML and SOAP handling, speed, many small features which are currently emulated at the API level in other languages ...and the cons: currently somewhat locked into MS' platform (though this should change shortly with Mono), somewhat inferior auto-documenting to javadoc.