Is there a reason I would use Knockout MVC instead of Knockout JS?

asp.net-mvc asp.net-mvc-3 knockout.js knockout-2.0 knockout-mvc
dotnetN00b picture dotnetN00b · Jul 23, 2012 · Viewed 18.2k times · Source

Another user suggested Knockout MVC to handle some AJAX posting issues. I read a little on it and I see it is a wrapper around Knockout JS. So I wonder what are the real differences between the two? Should I bother with Knockout JS since Knockout MVC exists? When would I use one over the other?

Answer

Kyeotic picture Kyeotic · Jul 23, 2012

Knockout MVC is the bastard child of WebForms. It routes all viewmodel methods through controller actions, meaning everything that happens has to bounce to the server and back. I cannot understand why anyone would take a framework like knockout, which is intended to be CLIENT SIDE MVVM, and force it to call the server for every function.

In addition, performing those methods on the server means the entire viewmodel needs to be passed to the server, and back to the client, for every function call. This is incredibly wasteful.

Using Knockout MVC means sacrificing all the performance benefits of client-side code for the benefit of not having to write javascript. The same trade-off WebForms made. It is not a good one. It is an antipattern.

If Knockout MVC dies tomorrow, the web will be a better place.

Related questions

How to use knockout.js with ASP.NET MVC ViewModels?

Bounty It's been awhile and I still have a couple outstanding questions. I hope by adding a bounty maybe these questions will get answered. How do you use html helpers with knockout.js Why was document ready needed to make …

Read More
Knockout + mvc 3 + Validation

In the controller I would like to be able to get to the client validation rules of the model. I've attached some attributes using data annotations and would like to be able to pass something back to the client via …

Read More
HTML.ActionLink vs Url.Action in ASP.NET Razor

Is there any difference between HTML.ActionLink vs Url.Action or they are just two ways of doing the same thing? When should I prefer one over the other?

Read More