Nothing on this project solves the real problems and introduces different ones, like how to have a reducer respond to different actions.
My quibble with React is that when you get into moderately complicated forms, you start sprinkling stuff all over the place to get the desired output.
Take for instance the most popular form library, redux-form. It's very heavy on it's own way of doing things, and there's a lot of stuff you have to know about it to be able to read into what the hell is going on, and it's hard to keep shit in the same place.
Reselect is also very heavy handed for what it does. I NEVER needed anything like reselect before redux, and it kinda went alright!
In my experience, for any reasonable development with redux you have to introduce:
reselect, redux-form, thunk, some sort of immutability (immutable or redux-orm), a sprinkle of compromises and plenty of boilerplate, or roll your own magic util functions (i actually rolled my own very similar stuff to rematch, for quick and dirty stuff).
When you summarise all that, it's really not that simple anymore!
By the time you get through all of that, you might aswell pick up angular with the added benefit of clearer best practices, nicer dependency injection (oh, but react calls it context so it's cooler!), familiarity and type safety.<p>It's kinda funny how redux succeeded with such heavy concepts, which is normally not the case. This is still a mistery to me.<p>Oh and don't get me started on HOC. Want a tooltip over your component? Sure, wrap it in tooltip HOC! Sooo much nicer than directives!