Any sufficiently complicated Flux app contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of KVO.
-
-
Replying to @ken_wheeler
@ken_wheeler@tomdale's argument is that you end up just modelling KVO in terms of Flux. Example: https://github.com/yahoo/flux-examples/blob/master/todo/actions/updateTodo.js …2 replies 1 retweet 3 likes -
Replying to @wycats
@wycats the whole point is that there aren't cascading updates.@tomdale@ken_wheeler2 replies 0 retweets 5 likes -
Replying to @floydophone
@floydophone Just so we're using the same language, what is an example of a cascading update?1 reply 0 retweets 0 likes -
Replying to @floydophone
@floydophone@tomdale Hm. Ember computed properties don't work this way. A CP doesn't synchronously update. It just carries the notification2 replies 0 retweets 0 likes -
Replying to @floydophone
@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 about1 reply 0 retweets 0 likes
@floydophone @tomdale I think understanding the totality of the events is pretty easy (and nice!) when the total number is small.
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.