-
-
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 -
Replying to @floydophone
@floydophone@tomdale Example: I have a "server updated article" event. If the article changed internally, should I trigger the event?1 reply 0 retweets 0 likes -
Replying to @wycats1 reply 0 retweets 0 likes
-
Replying to @floydophone
@floydophone@tomdale Hm. It's sounding a lot like a conventional "update" event a la KVO. No?3 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@floydophone@tomdale except the granularity chunkiness isn't keys right?1 reply 0 retweets 0 likes -
Replying to @krisselden
@wycats@floydophone@tomdale I meant to say granularity instead of chunkiness, I don't like not being able to edit tweets.1 reply 0 retweets 0 likes -
Replying to @krisselden
@krisselden@floydophone@tomdale Yes, I think granularity is a real difference. That's not usually what people say is good about Flux tho.2 replies 0 retweets 1 like -
Replying to @wycats
@wycats the granularity is exactly what me and people around me talk about.@krisselden@floydophone@tomdale1 reply 1 retweet 2 likes
@ryanflorence @krisselden @floydophone @tomdale I hear a lot of talk about one-way data flow, less about granularity. Links would be awesome
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.