Is context gonna end Redux's career?
With the React Hooks, problems are being solve! To use the hooks, we need to develop our app using functional components. We don't need to install additional package just to handle global states.
Example of functional component
function app(){
return ()
}
But is the Context hook enough to bury the Redux for good in the near future?
- What would be the advantage of Redux and Context?
It would be awesome if we could discuss it here. Opinions are welcome!
Top comments (9)
This is an interesting topic 👍 I think as times goes by we see an evolution in the tools available for the
ContextAPI. The point about debugging features forreduxis a big one, and packages likeredux-persistare also convenient. However, with a little elbow grease, we can attain these benefits for use with theContextAPI I'm lead to believe. For example, we can write our own customlocalStoragebased persistence forContext. And there are tools out there to help with debugging if theReact DevToolsare not enough. react-waterfall seems to be an option for usingredux-devtoolswith theContextAPI 👍Thank you for having interest in the topic.
The tools we use are improving and making it easier for the developers in creating their app. There are developers that is already refactoring from class component to function component, maybe because of the hooks?
Given that hooks are still young, they have a lot room for improvement and may take inspiration from older tools.
It's definitely an interesting space 👍
Nope, I believe that redux debugging features are already too well made and have already (sort of) taken control of the market.
Kind of like how most devs agree that svelte is a more efficient framework, yet still use react - it already has a powerful stance along with an ecosystem supporting it.
Yes, debugging in Redux is indeed too well made.
useReducer + useContext = redux , right ?
No.
Redux has a nice middlware, with which you can provide async or other (such as logging) functionalities.
And also all components using the context re-renders if the context changes, while Redux causes re-render only for components that subscribed to the changed data.
Redux also has a wide range of community (as it's not just for React) and the documentation is excellent, not to mention a good tooling support.
Context Hook and Reducer are good for developing apps that are not too small, and also not too complex. I love using Redux when the project is way too big.
maybe it's like Redux but not totally.