4 ms·

To be fair Dan Abramov, who wrote Redux, repeatedly tells folks they don't need it: https://medium.com/@dan_abramov/you-might-not-need-redux-be46360cf367#.pdph5

To be fair Dan Abramov, who wrote Redux, repeatedly tells folks they don't need it: https://medium.com/@dan_abramov/you-might-not-need-redux-be46360cf367#.pdph5d53q https://medium.com/@dan_abramov/you-might-not-need-redux-be4... Unfortunately, the general sense from the community is that it's an essential piece of the React ecosystem.

jasoncchild 10y ago
Dan is correct (naturally); depending on complexity and scope redux can be a drag. For a small project I will use an event emitter to communicate state change requests to my top level component. These sort of things tend to only have a handful of components anyhow.
shermablanca 10y ago
All respects to Dan Abramov, this is not necessarily true. Under the guidance of the right teacher, who knows the use cases and reasons for using redux with a React app, it can make perfect sense to learn them together. It's not easy, but most things worth it are not. There's a reason why many experienced developers choose Redux to manage the state of their React apps. Specially once you get into async and server-side rendering, you will want or need Redux middleware such as Redux-Thunk-- or perhaps you'd like to take it a step further into observables with RxJS and Redux-Observable. Perhaps these are all just a bunch of terms that you might not know that you need when you're first getting into React. But if you want performance and scalability -- and need an app that can withstand the pressures of today's demands -- then you may actually want to learn about all of these possibilities. But sure -- if you're just getting into react, then by all means learn React on its own. But if you're running a large production app, I would recommend that you use redux and perhaps RxJS in conjunction with it.
ninjaroar 10y ago
Part of me thinks that Redux is going to end up being the next Java EJB - really great and important concepts at the heart, but over-adopted in scenarios which don't need it. And in a few years, there will be a backlash about it due to too much code and complexity needed to do simple things.

jasoncchild 10y ago

Dan is correct (naturally); depending on complexity and scope redux can be a drag. For a small project I will use an event emitter to communicate state change requests to my top level component. These sort of things tend to only have a handful of components anyhow.

shermablanca 10y ago

All respects to Dan Abramov, this is not necessarily true. Under the guidance of the right teacher, who knows the use cases and reasons for using redux with a React app, it can make perfect sense to learn them together. It's not easy, but most things worth it are not. There's a reason why many experienced developers choose Redux to manage the state of their React apps. Specially once you get into async and server-side rendering, you will want or need Redux middleware such as Redux-Thunk-- or perhaps you'd like to take it a step further into observables with RxJS and Redux-Observable. Perhaps these are all just a bunch of terms that you might not know that you need when you're first getting into React. But if you want performance and scalability -- and need an app that can withstand the pressures of today's demands -- then you may actually want to learn about all of these possibilities. But sure -- if you're just getting into react, then by all means learn React on its own. But if you're running a large production app, I would recommend that you use redux and perhaps RxJS in conjunction with it.

ninjaroar 10y ago

Part of me thinks that Redux is going to end up being the next Java EJB - really great and important concepts at the heart, but over-adopted in scenarios which don't need it. And in a few years, there will be a backlash about it due to too much code and complexity needed to do simple things.