3 ms·

Why not just use KnockoutJS?

• aymeric 14y ago
  You can end up with a hard to maintain code with knockout.js if you don't structure it well. I found https://github.com/danderson00/knockout.composite https://github.com/danderson00/knockout.composite recently that seems to adopt a similar philosophy (pubsub) to what Flight does while keeping the benefit of knockout.
  • WickyNilliams 14y ago
    I've used this knockout extension to great success [1]. It's intuitive, it leverages knockout's internal pubsub, and fits in with the KO ethos. It can be used to synchronise observables across models (which is awesome as it's events without overhead), or as a general purpose event system. Ryan is one of the core contributors to knockout, by the way, so you can be assured of its quality. [1] http://www.knockmeout.net/2012/05/using-ko-native-pubsub.html http://www.knockmeout.net/2012/05/using-ko-native-pubsub.htm...
• 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.