3 ms·
It gets really hairy when you have to weave in asynchronous actions and things like react-thunk or react-saga. By the time you've wrapped your head around those
by cageface 10y ago
It gets really hairy when you have to weave in asynchronous actions and things like react-thunk or react-saga. By the time you've wrapped your head around those concepts as well the whole React stack doesn't feel quite as much like the breath of fresh air it does when you first start using it.
For my next Resct project I intend to go as far as I can with simple container components before I start pulling in the whole Redux toolkit.
- sotojuan 10y agoThis is why Ryan Florence (react-router, React Training) just made his keynote speech at the React Rally conference about people overusing Redux and not learning or wanting to use plain old React. In his trainings he constantly sees people trying to rush React and asking him about Redux (which he doesn't cover).
- tptacek 10y agoThis is also a drum that Dan Abramov (who created Redux) has been beating.
- tptacek 10y agoIt's interesting, I didn't find -thunk all that hard to grok, and in practice I was far less annoyed by that than I was by connect(). But I also found -thunk a refreshing change from what I'd been doing prior to redux (Flummox with async-await action creators).