Baroque EJB
The great thing about Java when it arrived was its simplicity and portability. Over time, the J2EE libraries have become pretty complex IMHO. For example, there have been many conversations on various news groups complaining about the learning curve and performance associated with EJB. .NET is definitely simpler than EJB for building server-side components, and so Java badly needs a new and simpler way to build portable and scalable server-side components.
I've been thinking for awhile that Sun's profligate way with Java APIs is becoming a problem. J2EE in particular takes on almost a Byzantine mainframe-like quality. As far as I can see, what usually gets put into practice are JSPs and servlets. The above is right though - we need a vastly simplified server side model for Enterprise Java. Right now EJBs are becoming far too unwieldy.
Comments
I like these suggestions for overall improvement of Java:
http://www.onjava.com/pub/a/onjava/2002/07/31/java3.html
Posted by: guryla | November 27, 2002 10:05 PM
I've been working with C#/ASP.NET stuff recently on my day job. As much as I generally dislike supporting Microsoft, I must admit I've had a pretty good experience with the language and environment. I like C#. My code tends to be prettier, simpler and more elegant than my java code was. And the .NET environment delivers on Java's promise of hotswapping compiled code -- I never actually had that work in the real world with java.
Uggh, I sound like a commercial. Somebody slap me.
Posted by: Luke | November 29, 2002 1:21 AM