mvc

Django and ASP.NET MVC

March 26th, 2009
While looking at some blogs and news sites about the MVC web-frameworks, I stumbled upon a nice stack overflow question:
ASP.NET MVC vs. Django - Which framework should I learn?
The answers have a lot of interesting points. For example one argument pro django by user saner is that:
Django is more mature and there are a lot of available components you can use. There is ORM so using database is very easy. Testing is simple and community is very responsive.
Another user, Oko, suggests that django is newbie friendly:
To start working with django, you don't have to be experienced Python programmer. If you are generally oriented in web development, you will find yourself working with django in no time.
For the ASP.NET MVC side of things, Lau Franco gives one possible advantage for people who don’t know neither of the frameworks:
…with ASP.NET MVC, you only need to learn the new framework. For Django, you also need to learn how to deploy, host and keep the site running (which means learning Apache and tools for dealing with it).
Regardless of whether the above opinion is true or not, I think ASP.NET MVC has a good chance of gaining traction in the developer world. After all there is a similar project that is already used by .NET programmers, and the most popular programming questions site currently uses (successfully) ASP.NET MVC on a large scale. I can think of a few more reasons why the new Microsoft framework will succeed and even outpace some lighter web frameworks (RoR, Django etc…):
  • ASP.NET MVC has a huge potential user base Considering how most of the businesses mindlessly follow in the path of any technology produced by Microsoft, I can just imagine the new craze (just like it was with class ASP.NET): ASP.NET MVC workshops, seminars, bible-books, training etc… Like it or not A LOT of programmers are going to be forced to use and learn ASP.NET MVC. Now, I am not saying this is necessarily a bad thing…
  • Great IDE/Tools support I am not saying that Visual Studio is the best IDE out there, but it does make certain things easy. For example adding a jQuery intellisense to Visual Studio is a breeze. There is also great support for ORM tools, whether you are using one or not. Other editors have similar to intellisense abilities, but they seldom combine everything in one package designed specifically for the target framework you are developing in.
  • Internet Exploder (rer) I don’t like internet explorer, but it’s a Microsoft product. Considering that Microsoft wasn’t focused on the web development much in the past (or at least they made it seem like they didn’t), I think we will see some advantage in having a personal browser to integrate things with. No other web framework currently has the luxury of having things “work” all the time with any kind of browser. If anything, Internet explorer will be a good test bed to try things out on.
I am at the end of my ramblings for tonight and going to go to bed. In the end, it will be interesting to see how the web-frameworks develop in the upcoming year. ASP.NET MVC is a welcome addition as it will challenge other frameworks to keep up, improve and improvise. More competition is a good thing, and I hope even MORE comes our way.