[dcoupl]

Its important to recognize that Backbone is a framework and Knockout is a library. These are very different things! Because of this, comparing Backbone and Knockout side-by-side is inappropriate; kinda like comparing a building with a vehicle.

For the record, Knockout handles way more than just forms. The statement that Knockout doesn't offer much beyond forms is simply false.

After writing code using both, on my next app I will use all of them: - Backbone for application structure and the client-side model layer functionality. Backbone is good at this. - Knockout to make handling user-triggered events a breeze, keep data in sync across views and layouts automatically, and to keep my markup and JS code tidy and separate with client-side templating. Knockout is good at this. - jQuery to interface with "low-level" constructs such as DOM elements. jQuery is good at this. In this set up, Backbone is the framework, Knockout is just another library being used, and jQuery is just another library being used. :-)