I use Knockout, too, and it has served me well. All the computed methods and model change detection are trivial in Knockout.
Knockout is only about data binding as far as I know, whereas Angular and Ember are full stack SPA frameworks. Also, while I'm a knockout fan, dealing with observables is not ideal when compared with plain old javascript objects that Angular allows you to bind with.
I agree, Angular has the right implementation. It's just not clear that it needs quite so much stuff to solve one problem. And if it isn't solving one problem, why not?
Re:AngularJS versus Ember
by Guillaume86 on Monday June 17, 2013 @07:09AM
(#5892473)
Angular team is going to split the Core into several small modules, hopefully a data-binding module will be available to replace knockout and do nothing more ;)
Re:AngularJS versus Ember
by KurtMueller on Saturday June 29, 2013 @09:12PM
(#5964325)
So what you're saying is they're trying to knockout knockout?
Re:AngularJS versus Ember
by steveklabnik on Sunday June 16, 2013 @04:37PM
(#5889848)
If you don't have much experience, how do you know they're too complicated?
You're right, I'm shooting my mouth off here, but this is the whole problem with these huge frameworks: they're so huge that, by the time you've spent the time to evaluate them properly, your objectivity is likely to be compromised. You'll never see an even handed comparison between the two.
This isn't unique to js frameworks. There's plenty of systems like this e.g. Hibernate. At least backbone was small enough that I could seriously evaluate it in a month long project. (For the record, I didn't like it, but at least I actually can have a considered opinion on it without being well past the point of no return.)
I'm happy to accept the problem is hard, but I doubt it's so complex it's impossible to decompose.