Great article from Dave, as always.<p>Worth noting that this is primarily about how Redux works with data flow in a React app, and doesn't go further into its other benefits, like predictability and debugging. I wrote some similar thoughts in a post I co-wrote for Full Stack React on why Redux is useful in a React app [0]. The Redux FAQ also helps answer "when should I use Redux?" [1].<p>For those looking to learn Redux, start with the official docs [2] and Dan Abramov's videos on Egghead [3]. My React/Redux links list [4] has an extensive list of additional tutorials and info.<p>[0] <a href="https://www.fullstackreact.com/articles/redux-with-mark-erikson/" rel="nofollow">https://www.fullstackreact.com/articles/redux-with-mark-erik...</a><p>[1] <a href="https://redux.js.org/docs/faq/General.html#general-when-to-use" rel="nofollow">https://redux.js.org/docs/faq/General.html#general-when-to-u...</a><p>[2] <a href="https://redux.js.org/" rel="nofollow">https://redux.js.org/</a><p>[3] <a href="https://egghead.io/series/getting-started-with-redux" rel="nofollow">https://egghead.io/series/getting-started-with-redux</a><p>[4] <a href="https://github.com/markerikson/react-redux-links" rel="nofollow">https://github.com/markerikson/react-redux-links</a>
For anyone who has read this post, I highly recommend you read through the comments--in my opinion the author has missed the point of Redux completely (at the time I am writing this reply), and there's a key thread in the comments section that tries to set things straight.