Redux – Not Dead Yet (2018)
blog.isquaredsoftware.com
Redux – Not Dead Yet (2018)
1–10 of 133 posts
Re: Redux – Not Dead Yet (2018)
#2Oh hey, that's my post.
I first wrote it back in 2018, and just updated it yesterday with some additional links and comparisons.
(Actually was considering retitling it after getting some feedback last night, but given that the link just got submitted here, I'll leave it as-is for now.)
A few quick notes:
- If you haven't looked at Redux in a while, please try out our official Redux Toolkit package [0], which is now our recommended approach for writing Redux logic, and the React-Redux hooks API [1]. We're going to be teaching both of those as the default approach for using Redux going forward.
- We have a new "Style Guide" docs page that gives our official guidance on suggested usage patterns [2]
- On that note, I'm working on an ongoing major rewrite of the Redux core docs [3]. My current task is creating a new "Quick Start" tutorial, which will be a "top-down" intro to using Redux to stand alongside the existing "bottom-up" tutorial sequence. The goal of the Quick Start section is to quickly introduce Redux concepts, and show RTK and hooks as the "right way to write Redux code", without going into the details of how it works under the hood, so that folks can get started now and learn the underlying aspects later. I've an early partial WIP draft PR up [4], and hope to finish the first draft in the next few days. Once the Quick Start page is done, I'll be turning my attention to rewriting the main tutorial sequence in order to remove outdated terms, clarify explanations, and teach simpler patterns (like using "ducks" files instead of splitting code across multiple files).
If anyone's got questions on anything I wrote in the article or otherwise Redux-related, ask away!
[0] https://redux-toolkit.js.org
[1] https://react-redux.js.org/api/hooks
[2] https://redux.js.org/style-guide/style-guide
Re: Redux – Not Dead Yet (2018)
#3I've recently tried using Redux for a side-project. While it solves the problem (organizing state), I feel there is too much boilerplate for my small project.
Are there any popular alternatives which don't use reducers?
EDIT: thanks for all the responses, I'll check them out :)
Re: Redux – Not Dead Yet (2018)
#4I don’t like the structure Redux forces my apps into. This might be a good opportunity to see what simple solutions people are using to avoid stuff like Redux. I remember reading about this:
Re: Redux – Not Dead Yet (2018)
#5I really think it should die, from a DDD perspective EDA should be handled as backend tasks with CQRS. If your api server isn't handling that then you really should stand up a BFF. I get that Redux is designed to handle all of that on the front end but it just doesn't belong there. I have seen too many projects devolve into garbage because they are trying to shoehorn too much crap into reducer patterns when it just doesn't belong there.
Re: Redux – Not Dead Yet (2018)
#6I've recently tried using Redux for a side-project. While it solves the problem (organizing state), I feel there is too much boilerplate for my small project. Are there any popular alternatives which don't use reducers? EDIT: thanks for all the responses, I'll check them out :)
hooks and the context api are great for small projects. Check out the hooks comparison section in the linked article to understand how it might fit your app. It references other good resources, too.
Re: Redux – Not Dead Yet (2018)
#7I've recently tried using Redux for a side-project. While it solves the problem (organizing state), I feel there is too much boilerplate for my small project. Are there any popular alternatives which don't use reducers? EDIT: thanks for all the responses, I'll check them out :)
There's stuff like MobX, but much of the point of Redux is the reducer step.
You may be happy with just using hooks, though.
Re: Redux – Not Dead Yet (2018)
#8I really think it should die, from a DDD perspective EDA should be handled as backend tasks with CQRS. If your api server isn't handling that then you really should stand up a BFF. I get that Redux is designed to handle all of that on the front end but it just doesn't belong there. I have seen too many projects devolve into garbage because they are trying to shoehorn too much crap into reducer patterns when it just d…
[deleted]
Re: Redux – Not Dead Yet (2018)
#9I've recently tried using Redux for a side-project. While it solves the problem (organizing state), I feel there is too much boilerplate for my small project. Are there any popular alternatives which don't use reducers? EDIT: thanks for all the responses, I'll check them out :)
You can use a React Context and have simple global state in your React app. If you like reducers, throw in a useReducer hook and you have a large part of what people use Redux for.
Re: Redux – Not Dead Yet (2018)
#10I agree ... I recently went back to using Redux in a project and I'm loving it. Redux at its heart is just a state manager, but because people tie it to React I've gotten people tell me all sorts things about how you don't need it anymore with all its new features.
I think the addition of React's hooks and context api actually make Redux easier to use, and I like the purity of its role as a state manager. I personally find that its cleaner to keep the overall application state in redux than to hold onto it inside of React, and leave react to manage its own component's state regarding ui level interactions.