Geeks With Blogs

News





INauseous() Shawn Cicoria - Solution Architect, Craftsman and Artisan - INauseous() - Main Blog Here: www.Cicoria.com

http://www.burtongroup.com/research_consulting/publicdoc.aspx?cid=70

This will surely heat up the Java vs. .NET war of words a bit...

Let me say first that the choice of platform makes no difference on whether an application can scale, perform, run reliably.  That's purely the physics of how things work and how some applications violate or push the laws of physics to a point that impacts performance enough to make them crappy applications.  I've worked on crappy applications built both on .NET and J2EE and I've also worked (refactored a few) on ones that excelled in meeting both the business and non-functional requirements.

Just take a look at the 8 fallacies of distributed computing (Peter Deutsch, 1994). Something that I've been referencing for some time, back to when it was just 7 fallacies - the 8th added by James Gosling a couple of years later.

What set's the platforms apart are the Tools, Code, and Guidance that the platform vendors and communities provide.  In that area, there is nothing on par with Microsoft and the communities around it.  But, we still got some work to do as well to keep the momentum moving forward.

In my past, I've worked with Java/J2EE (Websphere, Visual Age Java), CORBA, COM, DCE, blah, blah, blah.  I've personally experienced the pain of working with a base platform that's as confused as the war in Iraq.  When I moved "permanently" to .NET about 4 years ago (I did work with .NET when it was released June 2000 at the Orlando PDC and I was a Plural .NET Evangelist - now part of Dell Professional Services) I saw the "light".  It had the productivity and "oneness" that was missing from the other tools that I worked with before.

Here’s a couple of articles that discuss the momentum of .NET in an SOA world in comparison to J2EE/Java – basically that .NET is as comprehensive as J2EE but much easier to develop in.

Something that’s been an issue in the Java world is the complexity of their programming model with all the different component classes added through the community process over the years.  What they’ve ended up with is a inconsistent model that complicates design, development, deployment.

The article does go on to say that it’s boiling down to IBM & Microsoft with Eclipse & Visual Studio as the key platforms for development in an Services oriented world.

Analysts see Java EE dying in an SOA world

http://searchwebservices.techtarget.com/originalContent/0,289142,sid26_gci1198211,00.html

SOA gurus: .NET simpler than Java, but stuck in Windows

http://searchwebservices.techtarget.com/originalContent/0,289142,sid26_gci1204143,00.html

Posted on Monday, March 19, 2007 8:29 AM | Back to top


Comments on this post: JEE5: The Beginning of the End of Java EE...

Comments are closed.
Comments have been closed on this topic.
Copyright © Shawn Cicoria | Powered by: GeeksWithBlogs.net