4 ms·
I like knockout, I'm using it on a big project at the moment. Compared to say Angular it is definitely much easier to learn. My complaint (probably more relev
by TheAnimus 13y ago
I like knockout, I'm using it on a big project at the moment. Compared to say Angular it is definitely much easier to learn.
My complaint (probably more relevant to hardwaresofton) is that I like my MVVM to have a type resolution system, ok in javascript this is hard, but if I've got one ViewModel for the NavBar, it would be nice to be able to better state the one for the MainContentArea. ko.ApplyBinding(vm, someJQuery) just doesn't strike me as elegant!
- jasallen 13y agoI would argue its only easier to learn than Angular because it is smaller. Just data binding in AngularJS is much easier to me. That said, I liked knockout when looked at it, I just looked at Angular shortly after and fell in love. Annnd, I haven't looked at the new version, so grain of salt.
- taude 13y agoI like the way Angular manages nested $scopes a lot better than the ko.ApplyBinding paradigm. We are constantly have to add wrapper DIVs and clobbering each others ViewScope in Knockout.JS. It's not the end of the world, by any means.
- cmdkeen 13y agoI use a single viewmodel with multiple objects and the "with" binding to deliver that pretty effectively. You still get the ko.applyBinding(view) call but can have common HTML. We went to that after hell with pages littered with applyBinding calls.