If your app is simple enough, useState and useReducer can cover it, don't need it
If your app is quote complex ( in terms of actions and data model), you need to bring in quote a lot of other libs that make redux bearable ... but it's still gonna get very verbose.
It has a niche in my opinion, where your data model isn't that complex, but you have a lot of actions you can do on it.
I've used it extensively in the past in 2 very large apps, always gets annoying to maintain as you grow.
If your app is simple enough,
useState
anduseReducer
can cover it, don't need itIf your app is quote complex ( in terms of
actions
and data model), you need to bring in quote a lot of other libs that makeredux
bearable ... but it's still gonna get very verbose.It has a niche in my opinion, where your data model isn't that complex, but you have a lot of actions you can do on it.
I've used it extensively in the past in 2 very large apps, always gets annoying to maintain as you grow.
Yes!
useState
reduces a lot of pain 💓