+1 I owe a great debt to WebForms as the first 6 years or so of my career is based on it. Having said that, over time as I gained deeper understanding of a) how it works and b) what I should be doing instead, I found myself fighting the toolset more and more (to the point where I am currently working in WinForms).
What attracts me to MVC is not that it is shiny and new. It's that it solves the problems I had with WebForms in the first place. Sure it will have shiny new problems but if I don't like the way something is implemented I can throw that away and stick in my own implementation. On Fri, Mar 19, 2010 at 11:25 AM, Paul Stovell <[email protected]> wrote: > I think that if MVC had come out first, there either wouldn't have been Web > Forms, or it would have turned out very differently. For me the attraction > to MVC isn't that I like the MVC pattern or that I love dealing with HTTP, > or even that using new stuff makes me feel warm inside. It's that the code > in the implementation of MVC is so extensible and pluggable and well > designed, that I feel confident using it - there are no leaky abstractions, > and I can override just about anything I want. > > If MVC had been around first I think the .NET community would have had more > of a patterns and architecture focus and less of a "wiz-bang draggy-droppy > tool" focus. If Web Forms had then been invented, it would look very > different. > > Paul > > > > On Fri, Mar 19, 2010 at 9:26 AM, Richard Carde <[email protected]>wrote: > >> It's Friday... >> >> On 16 Mar 2010, at 22:24, Jonathan Parker <[email protected]> >> wrote: >> >> Keep a lookout for Umbraco 5 as well as this is going to be written in >> <http://ASP.NET>ASP.NET MVC. >> >> >> I see this a fair bit and wonder... "If ASP.NET MVC came out first, would >> people now be saying 'going to be [re-]written in ASP.NET Web Forms'"? >> *shudder* >> >> It's new... it must be better? >> >> I understand the benefits of MVC (or, more realistically, not using the >> abuse of HTML & HTTP that is WebForms) as I have a classic ASP background >> and good understanding of the protocols used on the Interwebs, but it just >> seems like people jump on the latest and greatest without understanding what >> that brings (good and bad). More XSS, etc. perhaps? Dunno. >> >> I know MVC has some helpers to properly encode output and that's great >> providing you know how/when/why one uses them. Same goes for outputting into >> strings used by JavaScript - watchout for the apostrophes and backslashes >> etc. >> >> <sarcasm>Thank goodness ASP.NET traps 'dodgy' characters like < and > in >> user supplied data</sarcasm> >> >> -- >> Richard Carde >> > > > > -- > Paul Stovell > -- Michael M. Minutillo Indiscriminate Information Sponge Blog: http://wolfbyte-net.blogspot.com
