title: Disadvantages of the ASP.net MVC Webforms View Engine?
body: <p>I'm planning a new project at the moment, built on MVC. Now, there are several different View Engines, and I just wonder what the disadvantages of the Webforms engine are that would justify a switch? Some people feel <a href="http://twitter.com/codinghorror/statuses/1515727133" rel="nofollow noreferrer">really strong</a> against it, and I just wonder why?</p>
  
  <p>Can I still retain something like .ascx Controls with other View Engines, say <a href="http://sparkviewengine.com/" rel="nofollow noreferrer">Spark</a> or <a href="http://code.google.com/p/string-template-view-engine-mvc" rel="nofollow noreferrer">StringTemplate</a>? (Okay, to be fair, that's just using RenderPartial and passing in proper ViewData, but it's still modularization of common "blocks" on multiple views)</p>