Hacker News Reader

Comment by tlrobinson | Hacker News Reader

I like the elegant simplicity of Redux, but it's so low-level and definitely feels like people are still figuring the "right" way to do a lot of things.

I tweeted my feelings on this last week:

    2015: reflux flummox redux marty alt fluxible…
    2016: redux-actions redux-act redux-forms redux-promise redux-ui…

https://twitter.com/tlrobinson/status/717258992989306880

View on HN

Heh. Can definitely vouch for that. I recently put together a links repo cataloging most of the Redux-related ecosystem, and was amazed at how many overlapping or similar libraries there were. 12 different promise middlewares, a couple dozen different side effects plugins, and I don't know _how_ many utilities to generate action creators, reducers, and constants.

The list is over at https://github.com/markerikson/redux-ecosystem-links if you want to look.

Thanks for putting that together! I'd discovered it a while ago and have been checking out all the utility libraries, trying to find ones that work the way I want. The funny thing is that so far none do, so I'm now working on one of my own...

I may change my tune six months from now, but part of the problem I see is that new people getting into React are told to not learn redux to "keep things simple." While it's a little bit of a pain to set up, redux (+ redux-thunk) ultimately reduces the amount of complexity and magic considerably.

Of you can write stateless functional components and have async and not use them, but the disadvantages of components without lifecycle methods appear much greater if you're just using vanilla React.

I think a better way to get into React is to start by watching the Redux videos and then apply React to the concepts you learned.

Reply on news.ycombinator.com