3 ms·
IMO the real question is why use KO when you know Angular? (except perhaps for the lib size) Really, I was using KO and it was really nice at the time but sinc
by Guillaume86 14y ago
IMO the real question is why use KO when you know Angular?
(except perhaps for the lib size)
Really, I was using KO and it was really nice at the time but since I've tried angularJS I don't see a reason to go back to KO.
Two way binding without ko.observable/ko.observableArray/ko.computed, just plain js objects is really a big win.