3 ms·
Having worked many years on mid to large scale React apps, I must say: In most cases component state (or useSate) and context works just fine. Why is everyone
by MoSattler 6y ago
Having worked many years on mid to large scale React apps, I must say:
In most cases component state (or useSate) and context works just fine.
Why is everyone so eager to add third party state libraries from the getgo? In most projects, Redux doesn't add net value.
- weeksie 6y agoI've been working with React since 2014 and I've never had a good experience with an app that relied entirely on component state. To each their own, perhaps you've discovered something I haven't. For me, Redux works very well with how I think about control flow. That said, my brain has been ruined by a youth misspent in fp land, so my preferences should be taken with a liberal application of salt.
- iimblack 6y agoComing from Clojurescript and using libraries like Re-Frame it feels much more natural to me to have a central store for most state. Sure I also use component state but I leave that for very simple cases. It seems like Context could also provide something like this but I'm not sure how it handles re-renders. If one part of my Context state is modified, do all Consumers re-render? Or just the ones that would be affected?
- jannotti 6y agoAll of them. I’d say that’s the biggest problem recoil is addressing.