A look through the yarn issue tracker tells me it's not time to try it again yet, since the last time it burned me. Maybe some day.
Redux is quickly being relegated to pile of don't use. I suspect 2020's survey result will show hooks to have completely destroyed redux.
Absolutely not the case. My own estimates are that around 50% of all React apps still use Redux, and the overall download numbers are continuing to increase consistently. I covered this in my Reactathon 2019 talk on "The State of Redux" [0], and my post "Redux - Not Dead Yet!" [1].
In addition, our new Redux Toolkit package [2] and React-Redux hooks API [3] are making it easier than ever to use Redux, and we've gotten a ton of very positive feedback from users who have adopted those APIs.
[0] https://blog.isquaredsoftware.com/2019/03/presentation-state...
[1] https://blog.isquaredsoftware.com/2018/03/redux-not-dead-yet...
Re:State of JavaScript 2019
by jeremy8883 on Friday December 20, 2019 @07:35AM
(#21843669)
I've never understood that position. Hooks and redux solve completely different problems. Why would the introduction of hooks change anything about using redux?
Seems like within React, Redux/Apollo/plain is splitting the data layer again too
But the yarn/npm is a tiny difference and data layer is much more application specific