4 ms·
Redux is great and it solves exactly that problem. You create a selector. You use the selector in a React component. The component re-renders when the selecto
by user43928 2mo ago
Redux is great and it solves exactly that problem.
You create a selector. You use the selector in a React component.
The component re-renders when the selector outputs a different value, with the usual reference equality caveat.
Does it get any simpler than that?
However, yes, I have seen most developers use Redux incompetently.
They would use actions like "setOrder" instead of "itemAdded", defeating the purpose of a state machine from the start.
- satvikpendem 2mo agoThey might have been using Redux before it did a major API change in the form of slices.
- user43928 2mo agoThat would be about 7 years ago, when Redux Toolkit released in 2019.
- satvikpendem 2mo agoThat's probably right. Lots of people migrated from Redux onto other state management libraries.
- Degorath 2mo agoThere's simply a ton of teams that also never updated. My previous team was not using RTK and our redux setup was extremely confusing to me (a backend engineer).