Interesting take. I think if you use redux toolkit it's a breeze, it has made managing that state really easy but yeah you're right that state management is a serious issues for whoever is starting to learn react.
I just looked at sinuous and i think you might run into same problem when you share the state between multiple components. Like which component is updating the state when and predicting what state will be after some action. I might be wrong here as I just took a look at it's docs. Could you share some resource on how to manage state accross components?
Also I do know that vue and sevelte also do state management really well you may also wanna look into those.
Redux-zero might be worth a look too... familiar stores, actions, middleware, support for Redux devtools with time-travel, etc. - just no reducers, making it quite a lot simpler. 🙂
Interesting take. I think if you use redux toolkit it's a breeze, it has made managing that state really easy but yeah you're right that state management is a serious issues for whoever is starting to learn react.
I just looked at sinuous and i think you might run into same problem when you share the state between multiple components. Like which component is updating the state when and predicting what state will be after some action. I might be wrong here as I just took a look at it's docs. Could you share some resource on how to manage state accross components?
Also I do know that vue and sevelte also do state management really well you may also wanna look into those.
Redux makes you write a lot of unnecessary code. Changing one action or adding new action leads to change of several files.
Try redux toolkit, it isn't the case anymore
Ok, I'll check it out. Thanks
Redux-zero might be worth a look too... familiar stores, actions, middleware, support for Redux devtools with time-travel, etc. - just no reducers, making it quite a lot simpler. 🙂
Thank you)
It still has mapDispatchToProps and stuff which I find a bit ugly. But yeah, still way better than taditional redux.