Any sufficiently complicated Flux app contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of KVO.
-
-
@wycats the whole point is that there aren't cascading updates.@tomdale@ken_wheeler -
@floydophone Just so we're using the same language, what is an example of a cascading update? -
@tomdale Any computed property that listens to another computed property. Stores can wait for others, but it's very restricted and explicit -
@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? - 7 more replies
New conversation -
-
-
@wycats argument? But I thought this was just a joke. -
@ryanflorence The hyperbole was a joke. Take out the joke framework and you're left with an argument. -
@wycats@ryanflorence clearly you get an argument either way, you two -
@lawnsea@ryanflorence I'm interested in an open debate about the "sideways" aspect of frameworks (KVO/Flux), not in slashing tires.
End of conversation
New conversation -
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.