VietMX Staff asked 3 years ago
Instead of saying downsides we can say that there are few compromises of using Redux over Flux. Those are as follows: 1. You will need to learn avoiding mutations: Flux is un-opinionated about mutating data, but Redux doesn’t like mutations and many packages complementary to Redux assume you never mutate the state. You can enforce this with dev-only packages like redux-immutable-state-invariant, Immutable.js, or your team to write non-mutative code. 2. You’re going to have to carefully pick your packages: While Flux explicitly doesn’t try to solve problems such as undo/redo, persistence, or forms, Redux has extension points such as middleware and store enhancers, and it has spawned a young but rich ecosystem. This means most packages are new ideas and haven’t received the critical mass of usage yet 3. There is no nice Flow integration yet: Flux currently lets you do very impressive static type checks which Redux doesn’t support yet.
