Any sufficiently complicated Flux app contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of KVO.
@floydophone @tomdale Hm. Ember computed properties don't work this way. A CP doesn't synchronously update. It just carries the notification
-
-
-
@floydophone@tomdale It's also not entirely clear to me that when you get to many dozens of events, ad-hoc events are easy to reason about -
-
@floydophone@tomdale Example: I have a "server updated article" event. If the article changed internally, should I trigger the event? -
@floydophone@tomdale Hm. It's sounding a lot like a conventional "update" event a la KVO. No? - 5 more replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.