jmarnold

I'm not sure why Django was brought into the mix. The view and callback function concepts in Django allow a workflow that is a lot less restrictive than say Rails or ASP.NET MVC.

Granted, I submitted the article because I'm one of the principal devs on the framework. However, see my comment above for clarity on what I think the message should be.

Take it all with a grain of salt. His point is more on a basis of principles and approaches to software design that builds on the quote: "It is practically impossible to teach OO design to students that have had a prior exposure to Rails".

Too many variables come into play when devs choose their framework of choice so it's quite the broad sweep to say "Let's put our framework against yours". I think the bigger point is: ".NET finally has some innovative approaches to the web"

We've learned from Rails, Django, etc and now we bring something new to the table. Regardless of the tone of the article, that's the message I would like to see be relayed