You&#x27;re absolutely right - the power and benefits of libraries like Redux are so obvious once you&#x27;ve grokked React but as a beginner it really is just going to slow you down or just get in the way of learning.<p>This is partly because of the overhead of having to learn another library, and partly because you have to learn by making mistakes, experiencing the pain, and then badly hand-implementing parts of Redux yourself to truly understand its value, and how it should be used. At that point you&#x27;re way beyond beginner level.<p>Same goes for &#x27;8. Use JSX, ES6, Babel, Webpack, and NPM&#x27; - JSX aside, setting up this tool stack is totally unnecessary for a beginner getting started hacking on a Hello World app. This is something you do after you&#x27;ve learned React, and you want to use use it in a &#x27;real&#x27; project. Depending on your knowledge of these tools it could take literally days of work to get started.<p>I&#x27;ll be honest, if someone with no knowledge of React asked me how to get into it, I&#x27;d also be tempted to mention Redux or Relay, the tool stack, all those things in the React ecosystem that are fantastic and essential for a real production React stack. But it&#x27;s just too much information, it&#x27;s not what a beginner wants or needs to know.<p>I think there&#x27;s a general lesson here - learning frameworks, how they fit together, and what tooling to use is really complicated and only seems &#x27;obvious&#x27; once you have the big picture. You have to remember what it felt like when you were a beginner, and just wanted to learn the basic rudiments of React itself - that&#x27;s more than complicated enough to get started with. When giving advice to beginners, it needs to be laser-focused, ignoring everything but the exact thing they&#x27;re interested in learning. Forget about all the extra stuff they&#x27;ll need in the &#x27;real world&#x27; - they&#x27;ll figure that out along the way anyway.