Any sufficiently complicated Flux app contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of KVO.
@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? -
@wycats@floydophone@tomdale except the granularity chunkiness isn't keys right? -
@wycats@floydophone@tomdale I meant to say granularity instead of chunkiness, I don't like not being able to edit tweets. -
@krisselden@floydophone@tomdale Yes, I think granularity is a real difference. That's not usually what people say is good about Flux tho. -
@wycats the granularity is exactly what me and people around me talk about.@krisselden@floydophone@tomdale - 1 more reply
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.