4 ms·
> The same thing in Backbone would have likely taken a lot more time and a lot more code. I think that's an unfounded (not to mention unfair) statement, unless
by k3n 14y ago
> The same thing in Backbone would have likely taken a lot more time and a lot more code.
I think that's an unfounded (not to mention unfair) statement, unless you've actually attempted to do so and can provide some objective data points. Otherwise, it's nothing but opinion.
Aside from that, the app does look interesting; I'll have to check it out later.
- MaybiusStrip 14y agoUnless we get a large number of developers to build the same application twice using each framework, all evidence related to this is going to be speculative or anecdotal at best. Having written a lot of both backbone and angular, I can confidently say that I am _much_ more productive with angular, so much that I get incredibly frustrated and resentful when I have to work on a backbone project. I think if you do a little bit of research you'll find a sizeable amount of similar testimony from people who have switched from backbone to a more comprehensive framework.
- ulisesrmzroche 14y agoOnce you start supporting persistence and keeping things reliably in sync, things start to get very complicated. You'd still have to write that out in Backbone, when ember or angular provide it out of the box.