J2EE vs .NET: The middleware company have done a wee study!

The PDF is worth a good hard read and the lessons learned are useful for anyone using either technology. Follow the serverside link to get to the report.

The server side thread on the subject

My post:-
Experience of the WSAD team does appear to be key here. The WSAD/WebSphere developers made some crucial errors that a couple of weeks experience or indeed a review of the freely available literature would have pointed out were complete folly. Why not break the timesheets down into time spent learning the product and time actually spend developing?

Further key bizarre decisions in the development process (like the lack of a code versioning and sharing tool as highlighted below) are incredible. This may not be fair but the J2EE developers did come across as quite naive.

However, I do concede the point that out of the box .NET is probably quicker to pick up and use - largely since one would use the common microsoft libraries and this means you don't have to make decisions/design common functionality and libraries. I do feel that with an established J2EE team with a framework that they are familiar with we would see far better developer performance.

Microsoft view:
http://www.eweek.com/article2/0,1759,1645550,00.asp