Every few months I review the top js frameworks and always come to the same conclusion: for existing projects you're probably better off sticking with what you'

Every few months I review the top js frameworks and always come to the same conclusion: for existing projects you're probably better off sticking with what you're already using. Each framework follows such a different paradigm that it's hard to transition incrementally, especially if you're app has a rich data layer rooted in an existing framework's mentality (in our case the backbone model/collection/sync mentality). I'd love a better view framework, but not if it requires a full rewrite of the model layer and all the related libraries. Until there's a ruby on rails quality model/collection/associations library that can be paired with a performant view framework with two-way data binding, I'll just stick with backbone where things are simple. Even if it costs me a few extra keystrokes. > A good rule of thumb is not to have more than 2,000 active bindings on the same page. Anyone personally run into this? What are you supposed to do in angular if you need to listen to change events for thousands of models?