<p>Well, all this time <span class="caps">ASP</span>.NET has been forgotten for real. Ruby on Rails, Django, Symphony and many others implemented something developers just loved: <a href="http://en.wikipedia.org/wiki/Model-view-controller"><span class="caps">MVC</span></a>. As Django&#8217;s co-creator <a href="http://www.holovaty.com/">Adrian</a> noticed in <a href="http://www.djangoproject.com/snakesandrubies/">Snakes and Rubies</a> (and RoR&#8217;s <a href="http://www.loudthinking.com/">David</a> agreed) is that the <span class="caps">MVC</span> pattern has the obvious advantage of having both webdesigners and developers working on the same project only on the stuff that matters to them.</p>

<p>When <a href="http://alcidesfonseca.com/blog/92">I tried to do something cool using <span class="caps">ASP</span>.NET</a>, it just didn&#8217;t fit my needs. It wasn&#8217;t <span class="caps">MVC</span> nor had the <span class="caps">AJAX</span> support I could have from rails, for example. I wished Microsoft (or anyone) had this awesome <span class="caps">MVC</span> framework!</p>

<p>Well, they have answered my prays: <a href="http://weblogs.asp.net/scottgu/about.aspx">Scott Guthrie</a> <a href="http://weblogs.asp.net/scottgu/archive/2007/10/14/asp-net-mvc-framework.aspx">announced in his blog</a> that yet this year the <span class="caps">ASP</span>.NET <span class="caps">MVC</span> Framework will be released and in the first half of next years it will be launched as a <span class="caps">ASP</span>.NET feature. I can&#8217;t say I&#8217;m not happy about this (obvious) decision to move <span class="caps">ASP</span>.NET into the <span class="caps">MVC</span> pattern! But somehow I just feel like Microsoft is always a step behind in this new web2.0 age.</p>