Via Simon Brunning I was pointed to this post, J2EE vs. NET, Java vs. C#, by Graham Glass.

It's an interesting read. I agree with his remarks about Java and C#. C# is a decent evolution of Java. There are a few point I don't like, for instance why reintroduce goto or why have to use virtual before you can use override? On the other hand attributes are very useful.

However, I disagree about with Mr. Glass about the relationship between .NET and J2EE. It may well be that J2EE appears more complex that .NET but I think this is for a very understandable reason. J2EE has been around a lot longer, and has been used to solve a greater range of real world problems than .NET. Sometimes it wasn't able to provide a solution, so things were added and J2EE has evolved to become more complex. .NET will go the same way; currently it looks simpler, in the way that Java was simpler in 1997, because it hasn't been around long enough to have to have it's limitations patched or overcome. I think there is a certain irreducible complexity in some problems and the framework used to solve them is going to have to address that, not everything is simple and easy to solve.