I can relate to some of the frustration in this article.
My team tried Redux/React/Immutable.js/ES6/Babel/Webpack for an in-house tool back in September. We knew Redux was immature but we did not realize the learning curve was so high. It’s not only Redux who is at “fault”, though. We came from a Backbone/REST API/ES5/AMD background and had to learn all the new concepts at once.
What we really struggled with in the beginning was understanding the concept of the action-reducer-state-view roundabout. It really is a totally different way of thinking as compared to MVC (or MV*). The breaking changes and constant updates of various packages (especially react-router/redux-router) was also a bit frustrating, but we chose an immature project so we can’t complain.