> it’s just a thing that lets you read and update a plain javascript object that different parts of your app can access

Doesn't require a library, let alone an ecosystem of libraries.

Why implement this functionality from scratch when a tried and tested implementation exists.

To eliminate a dependency.

So implementing everything from scratch has more benefits than a well maintained and documented dependency?

If it's simple, yeah. A redux-type store does not have to be complicated. there are certainly performance optimizations to using redux versus rolling your own, but that would only happen in very large applications.

I agree that you can roll your own store. You'll miss lot of free functionality and the dev tools, but maybe it's not stuff you need.

I also agree that introducing a dependency at every opportunity comes with serious drawbacks.

Every situation is unique of course. In my case: At work, I value code that is more standardised so that I get less bugs, documentation / best patterns and crucially easier on-boarding process. For a personal project, I would definitely consider rolling out my own implementation, even just for the learning it comes with.

Yes, I agree. There are trade-offs to be considered. Those are definitely benefits to using Redux, for sure.

The trade off makes no sense

I am kind of confused, because I view HN as a strong community in terms of development skill but the comments here on Redux are really surprising..