Wagnerblog

• I like it, but boy it requires a shift in thinking and has a learning curve since you need to practically relearn how to do everything on the web page. No more controls.
• It suffers a little bit from RoR envy.
• It will probably take some time before the best ways to do certain things in this framework will be discovered. Looks like everybody is trying new and different things.
• Because it does everything different than webforms it takes me longer to create something – that will change over time
• It drives home the point just how different web forms are from “normal” html based development because it lets you do things with CSS that you dont see in reg ASP.NET sites, because regular .net controls are not too open standards compliant.
• The separation of concerns into model / view and controller code is refreshing
• There will be a lot of open source feedback which will influence the next versions of MS MVC as well as offer substitute ways of doing things. Just like the RoR community, a MVC developer will be faced with a plethora of choices. I dont know how  I feel about that because it can lead to religious arguments — my Spark View Engine is better than you built in View Engine….use FubuMVC as opposed to MS MVC etc etc etc. Unless there is a clear frontrunner for a given aspect I am worried that there will be a lot of confusion.

Overall I still wonder how much need there will be for MVC in the long run as opposed to Silverlight or even something like Adobe Flex. In other words will the web move more toward Rich Apps or will it move more toward jazzed up HTML apps. Fact is there are things you can do in MVC that are not possible to build quite as nicely and easily in regular ASP.NET. For example there is a plethora of CSS tools out there and freely available plugins and whatnot for jQuery that may work easier in MVC pages.