This post seems to basically be "I love rails and ASP.NET is not Rails so it's inferior." Now I'm not saying the author is wrong for loving Rails, just that there was no way ASP.NET MVC could win in a rigged game so the comparison doesn't hold much weight.
To be a tad more specific...
1. A few of his issues are just wrong. The MVC team has been very open about including the community and taking contributions for example.
2. A lot of the author's comparisons are unfair because he's comparing a product that essesntially had it's first official release a few days ago to Rails. So complaints like "the community is too small" or "Microsoft might kill the project as a cost cutting measure" are not fair
3. A lot of his arguments are really the age old static vs dynamic language debate. I won't open that can of worms now but needless to say both sides have valid opinions. So it isn't fair to ding C# for that.
4. On another point Rails is what most call "opinionated software" while ASP.NET strives to give a lot of choices. So dinging ASP.NET for allowing the programmer to choose an ORM package that fits their needs doesn't seem really fair (Microsoft does provide one in the form of the Entity Framework)
Comments
This post seems to basically be "I love rails and ASP.NET is not Rails so it's inferior." Now I'm not saying the author is wrong for loving Rails, just that there was no way ASP.NET MVC could win in a rigged game so the comparison doesn't hold much weight.
To be a tad more specific...
1. A few of his issues are just wrong. The MVC team has been very open about including the community and taking contributions for example.
2. A lot of the author's comparisons are unfair because he's comparing a product that essesntially had it's first official release a few days ago to Rails. So complaints like "the community is too small" or "Microsoft might kill the project as a cost cutting measure" are not fair
3. A lot of his arguments are really the age old static vs dynamic language debate. I won't open that can of worms now but needless to say both sides have valid opinions. So it isn't fair to ding C# for that.
4. On another point Rails is what most call "opinionated software" while ASP.NET strives to give a lot of choices. So dinging ASP.NET for allowing the programmer to choose an ORM package that fits their needs doesn't seem really fair (Microsoft does provide one in the form of the Entity Framework)