> will reinvent lodash Someone who knows modern JS inside and out will see lodash as yet another unnecessary dependency. > Someone who doesn't know the purpos

> will reinvent lodash Someone who knows modern JS inside and out will see lodash as yet another unnecessary dependency. > Someone who doesn't know the purpose of Redux Knowing the purpose of Redux has nothing to do with knowing or using Redux. Write a couple medium-size apps in React. Congratulations, you now know the problems that Redux aims to solve. If your team doesn't have the discipline and experience to write a maintainable app without Redux, dropping Redux in isn't going to make it better and probably will make it worse. The main problem with modern Web dev is that we think it's necessary to solve every problem by layering on ever more and more shiny crap on top, rather than focusing on a small set of inescapable tools and mastering them. Want to be a React developer? Master HTTP, HTML, CSS, JS, and React. Then you'll know if you need lodash (nope) or a CSS framework (maybe) or Redux (probably not) and you'll be well equipped to make those decisions according to the project and team. Of course, if this wisdom were commonly heeded, we wouldn't have this: $ create-react-app foo && find foo/node_modules -type f | wc -l 20444 Which shows that in a modern "hello world" React app there are 20k files of dependencies installed out-of-the-box, with 900+ packages pulled from NPM. Good luck doing a security audit on that. And we probably wouldn't have "awesome" lists of only the 2000 most important things you need to know to be a modern web dev, either.