I get your point. But I think you have to see it from two directions: real world developing and teaching. When I wrote [The SoundCloud Client in React + Redux]

I get your point. But I think you have to see it from two directions: real world developing and teaching. When I wrote [The SoundCloud Client in React + Redux](http://www.robinwieruch.de/the-soundcloud-client-in-react-redux/ http://www.robinwieruch.de/the-soundcloud-client-in-react-re...) I made the mistake to think one could learn everything at once. I agree with your point that, when you are developing a more complex app, you will need some external state management eventually. But when you want to teach about one subject, I learned to stick to that subject and to teach it properly before students should dive into something else. I can't agree with your other point to use only Redux without React internal state management. Once your app grows more complex again, you don't want to store everything in your global store. (You shouldn't do so from the beginning.) In a development environment with multiple developers/teams you want to keep your store tidy. I had to learn that the hard way, because I made the mistake to learn React + Redux without React's internal state management in the beginning.