like you, I also came from backbone.js and since then I have switched to CanJs. Backbone.js open endedness if I may compare to UX concept, is too open ended that it can cause analysis paralysis. There is no defined path for programmers to take. Of course this is not a bad thing, it's just different from what I would like.
CanJs takes care of live binding, memory management, syntatic sugar, etc, it feels to me it's like a backbone with everything that I want already built in. I have tried other frameworks too such as ember or angular, and I have to say, even though they are all in the same family (javascript mvc framework) but they target different types of customers (developers) and variety is good.
Comments
like you, I also came from backbone.js and since then I have switched to CanJs. Backbone.js open endedness if I may compare to UX concept, is too open ended that it can cause analysis paralysis. There is no defined path for programmers to take. Of course this is not a bad thing, it's just different from what I would like.
CanJs takes care of live binding, memory management, syntatic sugar, etc, it feels to me it's like a backbone with everything that I want already built in. I have tried other frameworks too such as ember or angular, and I have to say, even though they are all in the same family (javascript mvc framework) but they target different types of customers (developers) and variety is good.