Last month I started learning redux and the learning process transformed me from skeptic to believer. I decided to record a short screencast to document what I learned and show why I think it's a great paradigm for managing state in your javascript applications.
The part I found most useful was that it truly helped me learn what data-down-actions-up (DDAU) should look like when done well. One painful pattern I've seen in my own ember apps late last year was that the route started to grow. It was responding to actions that previously would be handled in the controller/or component itself. In addition, because each mutation is now explicit these actions grow in number (almost making me feel like a new object with the role of mutation manager should exist at times).
With redux I found you actually get this as a pure function. The function is called a reducer and it's job/role is to take an action and the previous state => then return a new state. Another added benefit of this approach is that all your data structures become mutation free (something you start to ask about when you get past hello world/todo-mvc).
