Why ASP.NET MVC is Bad

Can you tell me why ASP.NET MVC is bad?

ASP.net MVC is almost a necessity to use JavaScript heavy, interactive web pages. And ASP.net MVC lets you set up multiple webpages that vary based on the language the user selects.

Then why do so many people consider it bad? Aside from the people working with ASP.net 1.1?

ASP.net MVC is not a good choice if you have a lot of server side code.

That's true of ASP.net, too.

One of the weaknesses of MVC with ASP.net is that it is newer than ASP.net. The conventions and best practices are not as set, and there is not as much out there as dot-net.

Web forms are a standard feature online. Why not just use web forms to keep things simple?

ASP.net MVC is not a good idea if you have tons of Web Forms. If you love web forms, stick with ASP.net.

Web forms allow you to have rapid application development.

That's pretty much a necessity given that you can't re-use them from instance to instance.

MVC lets you re-use a lot of code, improving productivity overall even if there is a learning curve.

MVC supports code module re-use, but ASP.net MVC really doesn't.

I thought they had a lot of built in features to make things efficient in addition to its built in controls.

ASP.net MVC has a horrible routing API. Don't use ASP.net MVC if you have a lot of controls.

So what should I do?

Implement MVC but without ASP.net. Or use ASP.net through Sharepoint for a point and click development interface.

And all of this is on top of the learning curve.

ASP.net has a modest learning curve, but the fact that it is only used by Microsoft means that you'll have tons of headaches using it.

At least MVC allows you to get away from the state issues you see with web forms.

You can save yourself that problem by abandoning ASP.net altogether.

[glialcell]

-_- Useless video pointlessly bashing ASP.net and Microsoft. I hate them both as much as the next guy, but you had hardly any points, other than that it's user base is really small, which isn't even much of a point.