For asp.net mvc which js best either AngularJs or BackboneJs or KnockOutJs ?

• It is based on the origin of the application.  The detail is very so answering is difficult . The Backbone is easiest  and also work in angular js is good .
• Performance is high in coder than the framework, in general.
• If doing heavy DOM manipulation then  use jquery and backbone
• For very data driven app then use the Angular with it’s nice data binding
• For Game programming then use direct to canvas, maybe a game engine – Source

    Have a glance at this link :  https://stackoverflow.com/questions/5112899/knockout-js-vs-backbone-js

    This link also provide more information :

    http://www.infoq.com/research/top-javascript-mvc-frameworks

    Using the  Angular is very good  just because of its performance, but there are plenty of reasons .

    For developing single page application ,a SPA framework is needed . It including 2-way data-binding , client-side routing, page composition, navigation, screen state management, module system, bundling . Choose between Angular and Durandal is user choice .

     Both the angular and durandal are very similar functionality, but, Durandal is the most complete SPA framework, which is very easy to use. Both Durandal and Angular can be used with Breezejs to develop data centric applications.

    Check Durandal, Durandal Auth and HotTowel Angular .

    For developing ASP.NET MVC application, In the client side  do the two-way data binding to minimise DOM manipulations.  It’s an overkill to use angular just for data-binding. Backbone or Knockout are super , but Angular is quite good.

    The Knockout  is used with ASP.NET MVC/Web API at work, but angular js is also  good . Knockout done   only the easy problem than does Angular, the latter is being a perfect SPA framework .

    For checking apples to apples , Then consider the Knockout in tandem with Durandal, as this is a full-blown SPA framework like Angular.

    The  memory leaks are simple to prevent with Angular than Knockout, since Knockout give references implicitly as user subscribe to observables  and there is some hard time in trying to trace  such memory leaks due to undiciplined taking of Knockout subscriptions without cleaning up.

    With Angular ,the same problem is not coming , as user is not subscribe directly to mutating variables . Instead, the framework is in total control of applying model changes, which is harder initially , but ultimately leads to better maintainability.