-
-
Notifications
You must be signed in to change notification settings - Fork 15.2k
Closed
Labels
Description
“Atomic Flux with hot reloading” was enough to spark interest but is there a better way we can position ourselves now?
What I believe to be key ideas of Redux:
- Ecosystem for great developer experience. Hot reloading, devtools with replay of actions as you change the code, time travel and error handling, dev session persistence, crash reporting are all easy to do outside the core.
- Contracts over privileged APIs. If you look at 1.0 branch, there isn't really much API surface. We're not doing modularity for modularity's sake. It just so happens that not locking people into a particular APIs and instead suggesting to implement contracts (e.g. a reducer contract) has many benefits: people are able to migrate to (and from) Redux easily by building small adaptors (e.g. a
ReducerStorefor Flux library they're using). This also lets us have a bigger interoperable ecosystem, as even the devtools for Redux can be adapted to work with other Flux frameworks. - Only concerned with managing state mutation. Redux doesn't care what you use for state (plain objects, ImmutableJS, Mori), it doesn't care what you use for updating the views (React, Angular), it also doesn't care how you orchestrate async (e.g. Rx).
What do you think? Is there a better tagline for Redux 1.0?