Thu, Jun 23 2005 9:54 AM Ernst Wolthaus

There’s More to Java vs. .NET Than Technology

A new colleague of mine, Raynni Jourdain (LogicaCMG, Arnhem), pointed me towards this article about Java vs. .NET.

In short, it says .NET for projects that have ease-of-use, need quick time to market and a lifespan of 2-5 years and Java for more complex projects, scalability and a lifespan of 5-10 years.
I'm not a Java expert, but I think I disagree...

Why couldn't you build complex projects with .NET? I think you can...!

When it comes to .NET vs Java, the words of an classic Irving Berlin song come to mind:
“Anything you can do, I can do better
I can do any thing better than you...“

With .NET, you can build reliable, fast, complex solutions, just as well (in fact, even better, because of the better tools available) as with Java/J2EE.

I see one problem, however....

A lot of times, MS (Microsoft) technology is used to rush to get results fast. And MS technology gives this ability.
MS projects are quicker to market but (because of the rush) sometimes suffer some quality issues.
On the other hand, when using Java/J2EE, it is accepted that development takes longer because it's more 'complex'...
And so it becomes a selffullfilling prophecy (try typing that without a typo ;-)) that Java is more robust...

If managers and business would deal with MS projects the same as with Java projects (time and budget), the MS consultants would get the chance to prove MS technology is ready for complex, enterprise-level solutions.

What do you think?

Filed under: , ,

# re: There’s More to Java vs. .NET Than Technology

Thursday, June 23, 2005 10:30 AM by Ernst Wolthaus

Totally agree. It's just another "My technology is better than yours", when we all know Microsoft rules!!!

# re: There’s More to Java vs. .NET Than Technology

Saturday, June 25, 2005 1:32 AM by Ernst Wolthaus

I am not convinced (and I am definitely a .NET person). The Java guys have a better choice of frameworks that also tend to be more mature. Because Java has been around longer more libraries seem to be available as well. A recent example I encountered recently is the availiability of a HL7 implementation (a dominant comms protocol stack in the health market). I have also seen implementations of open source workflow & transaction managers in Java as well as businesss rule engines. In the MS world a lot of this is hard to find, and when it can be found it often is ported from Java!

The impression I get is that MS developers have more experience on the UI side, whereas in the Java community the weight is more on the logic behind the UI. That fits with the traditional strengths of Microsoft's tools and where the bulk of their money comes from (Windows Client & Office).

# Blog link of the week 25

Sunday, June 26, 2005 6:20 PM by TrackBack

Blog link of the week 25

# re: There’s More to Java vs. .NET Than Technology

Monday, June 27, 2005 8:56 AM by Ernst Wolthaus

Dear Gerke,

The strongpoints you name of Java have (imho) nothing to do with the strength of Java, but more with the longer time on the market of Java. Yes, Java was introduced years before .NET, so that would explain that there are more specific implementations.

But what I meant was:
If you compare Java to .NET (C#), is there any reason you would choose Java over .NET, over vice versa? (apart from certain tools and implementations)

I don't think so!
You can build complex business logic with .NET just as well as Java.

"The Punchline"
So, if you can do enterprise-level software with C#, and the tools (VS.NET) are better (most reports agree on this one), why would anyone choose Java over .NET???

# re: There’s More to Java vs. .NET Than Technology

Monday, June 27, 2005 8:58 AM by Ernst Wolthaus

Perhaps I should mention I'll be joining Avanade (www.avanade.nl) in August.

Avanade is a joint-venture of Accenture and Microsoft, so maybe, just maybe, I'm a bit biased.... ;-)

# re: There’s More to Java vs. .NET Than Technology

Tuesday, September 06, 2005 11:00 PM by Sebastian Andersson

Not to start a flame war, but in what situations are VS.NET better than Java IDEs like IntelliJ IDEA, Eclipse or NetBeans? I've only spent a year developing in VB.Net so I might have missed out on a lot of good things in VS.Net, but it is rare that a whole day goes by without VS.Net doesn't hang or the application doesn't start on the first try with when started in debugging mode (leading to yet another verification that the files doesn't need to be recompiled before starting it again). When starting nunit-gui from the debugger to be able to debug/examine the unit tests, there is a 10% chance that the whole VS.Net hangs, having to kill it with the task manager... We develop a client/server solution where some projects are shared between the client and server solutions (to make the startup of VS.Net not so incredibly slow). We can't have both "solutions" open at the same time due to file locking, so we have to close one solution and open the other, which takes forever! All of these are little time thieves that together steal an hour a day for us. The tool would have to have some really good features to help us make up that lost time, but so far I've found little besides the stored procedure debugger (which can't view temporal tables...) that is of any value to me. For pure GUI applications (and perhaps web applications that I do not developed), perhaps it is good, I don't know, but for pure "coding" there isn't much there, even navigating between different files is a PITA. A simple keep X files open, close the LRU seemed to be a too hard setting for them. When VS.Net 2003 came out, I used IntelliJ IDEA which was, and still is a pure joy to program in. Who calls this method? A keystroke away and I got a real list of possible callers, not just a textual search. Refactoring was as easy as cut & paste. There was lots of warnings about code that is probably incorrect, unlike VB.Net where even errors are sometimes accepted (like having the same case-target twice in a switch/select statement)... And so on. Today all the major IDEs for Java are leaps beyond what I've used of VS.Net. But as I've said, I've only used it for a year and 99% of the time it has been for writing code, not GUI nor web-work. Perhaps it is much better if one uses C#?

Leave a Comment

(required) 
(required) 
(optional)
(required) 
Please add 8 and 6 and type the answer here: