Second, "modern Redux" is considerably different than the Redux code people might have seen in the past. In particular, we now teach people to use our official Redux Toolkit package as the standard approach for writing Redux logic. It includes utilities to simplify several common Redux use cases, including store setup, defining reducers, immutable update logic, and even creating entire "slices" of state at once:
The React-Redux hooks API also makes it easier to use Redux in their React components.
Finally, we've added a "Redux Essentials" tutorial in our core docs, which teaches beginners "how to use Redux, the right way", using our latest recommended tools and practices like RTK and the React-Redux hooks:
Hi, I'm a Redux maintainer. A few quick thoughts:
First, I've written articles and discussed when and why it makes sense to use Redux, as well as how Redux compares to various other tools and options:
Second, "modern Redux" is considerably different than the Redux code people might have seen in the past. In particular, we now teach people to use our official Redux Toolkit package as the standard approach for writing Redux logic. It includes utilities to simplify several common Redux use cases, including store setup, defining reducers, immutable update logic, and even creating entire "slices" of state at once:
redux-toolkit.js.org
The React-Redux hooks API also makes it easier to use Redux in their React components.
Finally, we've added a "Redux Essentials" tutorial in our core docs, which teaches beginners "how to use Redux, the right way", using our latest recommended tools and practices like RTK and the React-Redux hooks:
redux.js.org/tutorials/essentials/...
I've also just published a new "Redux Fundamentals" tutorial that teaches "how Redux works, from the ground up". That tutorial is now live:
redux.js.org/tutorials/fundamental...
I am honored to have a redux maintainer here. Thanks a lot for your input!