This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: The light slowly dawns
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Richard Monson-Haefel notes the complexity of J2EE development, and says that it needs a simpler programming model:
Over the past four years the various J2EE APIs (EJB, Servlets, JDBC, etc.) have become more and more sophisticated and, unfortunately, more complicated. As a result the learning curve has become ridiculously steep " for every API in J2EE there are dozens of types and hundreds of methods and a bazillion books designed to make them easier to understand. The increase in sophistication is necessary because enterprise software is inherently complicated, but do the APIs need to reflect the complexity of the underlying systems or should they hide the complexity? I argue that the J2EE APIs should reflect complexity as well as hide it by offering both implicit and explicit programming models.
Now, complexity of this sort is hardly limited to Java, even if J2EE is a particularly bad example of it. It's what happens when you allow a bunch of people who don't seem to understand distribution to build a framework around it....
Previous Topic
