[bananas]

Agree entirely. However from an architectural POV, Asp.net has always been a pile of crap because everything is abstract classes and sealed ones at that. Virtually impossible to reliably test. Interfaces? Never! Even System.Web.Abstractions stinks.

Having written a view engine, security frameworks, NH session management stuff, 100+ complicated controllers, action filters galore and thrown it into MVC I've come to not appreciate it very much.

And don't get me started on Razor. Buffered rendering for layouts (bye bye RAM), batshit source, obtuse and non orthogonal syntax, poor runtime integration, absolutely no separation of logic and code.

I'm ready to move on.

Edit: just to add, I'm really liking Java's design by committee approach these days. It's incredibly clear that you need a lot of opinions to build a correct and well engineered solution. With .Net in general, it's served up to customers ike a soup kitchen. Occasionally we're left without soup though (WF3, Silverlight, early EF versions, WCF fragmentation, razor and so forth). The majority of the praise comes from people subjected to WebForms for years or even Telerik circa 2006 at the worst.