@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 …
@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 -
@ryanflorence@krisselden@floydophone@tomdale I hear a lot of talk about one-way data flow, less about granularity. Links would be awesome
End of conversation
New conversation -
-
-
@wycats@floydophone@tomdale Flux stores don't alert one another that they have changed. They only alert the view and expose getters. -
@fisherwebdev@floydophone@tomdale We made a mistake with making components use two-way bindings by default, but that's a diff. thing.
End of conversation
New conversation -
-
-
@wycats No. One action at a time is all Flux allows. Stores can listen to updates without coupling to action creator@floydophone@tomdale -
@BrianDiPalma1@floydophone@tomdale What does it mean exactly to support "one action at a time"? -
@wycats if action A is being processed Dispatcher prevents action B from being processed, no event chains@floydophone@tomdale -
@wycats@briandipalma1@floydophone@tomdale To clarify, Dispatcher throws if you try to dispatch an action while dispatching an action.
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.