I can't count the number of people in the past few years that have asked me to weigh in on the Java vs. .NET debate. You'll find my answer here, and the answer is simple. It is the only answer I know.
It depends.
Heh.
It does depend, but--for the most part--it is all about choice. In Java, you get a lot of choices. Open source vs. commercial, this platform, that platform; EJB, Pojo; Spring, Struts, Pico, foo, bar, blah blah blah. And therein lies one of the biggest problems with Java -- you have to make choices. And those choices can be non-trivial in light of the intricate version dependencies that can ensue.
With .NET on the other hand, you don't have nearly so many choices most of the time. Most of the time, you eat what Microsoft puts on your plate, and you like it, or you go to bed hungry. Most of the time, though, it is good enough.
And so you can focus on bottom-line, droll things like your business domain. You still have to focus on those things in Java, of course, you just have to after you have selected your platform, container, and so on.
That being said, it sure is nice to have some of the choices you have readily, freely available to you in Java. Like Active MQ.
So, given a choice between .NET and Java, I'd rather be doing Ruby.
Recent Comments