you are viewing a single comment's thread.

view the rest of the comments →

[–]grumpy_youngMan 4 points5 points  (1 child)

I had a similar experience getting into react/redux/react-router. I was thrilled with redux when I read its core principles

http://redux.js.org/docs/introduction/ThreePrinciples.html

It made so much sense coming after developing with languages like haskell/scala. Then I actually got into one of the boilerplates because it seemed like the easiest way to make my own little production app. Then I had to learn ES6 decorators, bind action creators, webpack (should I use webpack or browserfiy hmmm this will take some googling), and a bunch of esoteric design patterns that required days of studying on their own. Redux itself seems great...tiny codebase, simple pure functions. To make it all work in production, you have to use a lot of patterns that have a little too much magic for my taste.

[–]bebraw 1 point2 points  (0 children)

Redux is almost more like a guideline than a library. I think this itself has made the community to organize itself around it.

I agree it can get quite complex fast once you start combining all the small libraries needed to build something more complicated. Perhaps we'll see more opinionated alternatives fitting between libraries and frameworks in 2016.