It is a lot more clear from the description on https://github.com/kmalakoff/knockback https://github.com/kmalakoff/knockback what this is about: When I was eva

It is a lot more clear from the description on https://github.com/kmalakoff/knockback https://github.com/kmalakoff/knockback what this is about: When I was evaluating client-side frameworks, I liked lots of the pieces, but wanted to "mix and match" the best features. I started with Backbone.js and really loved the Models and Collections, and used Brunch to get me up and running quickly. After a while, I found the view coding too slow so I wrote Mixin.js to extract out reusable aspects of my views. When I was looking for my next productivity increase, an ex-work colleague suggested Sproutcore, but at the time, it wasn't yet micro-frameworky enough meaning I would need to learn something big and "to throw the baby out with the bathwater" as they say (it is hard to give up Backbone models and collections!). Then, I discovered Knockout and knew it was for me! Knockout provided just the right building blocks for a layer between my templates and data. As I used it more, I built additional functionality like Backbone.ModelRefs for lazy model loading, localization helpers for truly dynamic views, and most recently, an easier way to sync collections and their model's view models. So here it is...the refactored and shareable version of my Backbone bindings for Knockout: Knockback.js