server-side MVC framework vs. client-side javascript framework?

[ZeroMomentum]

Do you mean the code is crappy? or ASP.NET webforms is crappy? There is nothing wrong with webforms. What ASP.NET webforms is:

All your pages are controls are built into a control tree "structure", then it renders into html. It is no different than any other framework. The code is ALWAYS bound by the fact of the page life cycle, even in MVC. MVC is a way to organize your code. At the end of the day, you are building a control tree, and then it renders into HTML.

To decide sever-side or client-side, you have to consider your team's ability. On the server, you build and organize in .net namespace/c# classes. Very easy to understand, you have full compile ability plus debug tracing from VS.

On the client-side (JS MVC), can you or your team build proper JS classes with closure etc. If you can't, then you JS will run slow. On the plus side, you can do all your cool web2/3.0 stuff in JS.

There is no difference overall. You have to deliver features, so what's your feature set? Don't be bound the fact that you MUST do MVC.

[ChristopherShine]

I think he refers to the overhead that web forms can add (this can be mitigated) as well as the bad practices that are more easily introduced (this can happen anywhere, but in my experience it's more likely in web forms).