Truthfully, if MVC came before WebForms, people wouldn't have flocked to the .NET platform like they did. There was a reason that WebForms was so successful - it mimic'd the existing drag and drop paradigm that VB6 developers were used to. Had I
________________________________ From: ozdotnet-boun...@ozdotnet.com [ozdotnet-boun...@ozdotnet.com] on behalf of Paul Stovell [p...@paulstovell.com] Sent: Thursday, March 18, 2010 8:25 PM To: ozDotNet Subject: Re: ASP.NET Web Forms vs MVC vs ... 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 <rich...@carde.id.au<mailto:rich...@carde.id.au>> wrote: It's Friday... On 16 Mar 2010, at 22:24, Jonathan Parker <jonathanparkerem...@gmail.com<mailto:jonathanparkerem...@gmail.com>> wrote: Keep a lookout for Umbraco 5 as well as this is going to be written in <http://ASP.NET> ASP.NET<http://ASP.NET> MVC. I see this a fair bit and wonder... "If ASP.NET<http://ASP.NET> MVC came out first, would people now be saying 'going to be [re-]written in ASP.NET<http://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<http://ASP.NET> traps 'dodgy' characters like < and > in user supplied data</sarcasm> -- Richard Carde -- Paul Stovell
