3 ms·

redux composes stores into one, and discourages the "web of connections": https://github.com/gaearon/redux https://github.com/gaearon/redux It is rather immatu

• chrisconley 11y ago
  While we're not using Redux in production yet, it's been an amazing library to work with so far.
• nuschk 11y ago
  We're also using redux in production, after having switched from reflux. In redux, it's so much more clear where to put stuff. In reflux, it was never clear to us whether certain async server operations should be handled in stores or in the actions. In general, you would always want them to be with your actions. Though every time you need a store variable to do the server call, you end up putting code in the store again (or passing the needed state through your react components, which is even uglier). Not so in redux, where you have access to the stores in your actions. This way, stores get really dumb, which is the way they should be IMO. And, btw, replacing reflux by redux is relatively easy and straightforward, as the same general concepts (flux) apply. I also find the redux code easier to read, as the whole library is doing less (while achieving the same).