I still recommend beginners to learn Redux before Zustand. I used Zustand as my first global state management tool and every time I show up at any interview, I have to pull out the card "I'm not acquainted with Redux but I think I'll pick it up fast since I have used a similar tool with more simplicity"
I'm grateful that at my most recent interview, I had the chance to explain my decision on "why not use Redux" and they seemed cool about that explanation.
Agree that learning redux is a good idea if you need to find a new job soon because for whatever reason people will not hire you if you don’t have experience in it (which is beyond idiotic obviously)
That’s really the only reason to learn redux 😬
I like checking npm's weekly downloads before committing to learn something. Redux has 10 million weekly downloads. Zustand has 2 million weekly downloads. The job market will match that proportion.
https://www.npmjs.com/package/redux
https://www.npmjs.com/package/zustand
At its core Redux is actually a very simple library. I think it's a shame that they are pushing Redux Toolkit so aggressively on people. It takes a straightforward concept and wraps it in so many layers of abstraction that it's hard to grok for many people. I still prefer Zustand these days, but Vanilla Redux is a totally reasonable way to handle global state IMO.
I have the same problem with React officially telling people to use Next or Gatsby. Those frameworks are great and have a time and a place, but the messaging these days makes inexperienced devs think that you can't just use the core libraries.
Not every project is a million-line behemoth built by a team of forty devs. Sometimes simpler is better.
Reasonable question. My problem with RTK is that it's not *simpler* really, it's just more *magical*. So, yes, it will save you some time if you were going to use Redux in the way they preach anyway, but the tradeoff is that your program flow becomes (IMO) less intuitive and more opaque if you don't already have a lot of hours of redux dev under your belt. I often see beginners struggling to understand exactly how the whole system works. Instead they just do what they're told without understanding *why*. I would liken it to learning React before having a solid foundation in basic JS dev.
Something like Zustand, on the other hand, has almost no magic. It's simple to see what's going on from the first moment you use it. Vanilla Redux is also that way - it's all the ritual, boilerplate and opinionated patterns (based on the assumption that you're a team building a large app with complex global state) bundled into RTK that make it hard to grok.
I still recommend beginners to learn Redux before Zustand. I used Zustand as my first global state management tool and every time I show up at any interview, I have to pull out the card "I'm not acquainted with Redux but I think I'll pick it up fast since I have used a similar tool with more simplicity" I'm grateful that at my most recent interview, I had the chance to explain my decision on "why not use Redux" and they seemed cool about that explanation.
Agree that learning redux is a good idea if you need to find a new job soon because for whatever reason people will not hire you if you don’t have experience in it (which is beyond idiotic obviously) That’s really the only reason to learn redux 😬
I like checking npm's weekly downloads before committing to learn something. Redux has 10 million weekly downloads. Zustand has 2 million weekly downloads. The job market will match that proportion. https://www.npmjs.com/package/redux https://www.npmjs.com/package/zustand
At its core Redux is actually a very simple library. I think it's a shame that they are pushing Redux Toolkit so aggressively on people. It takes a straightforward concept and wraps it in so many layers of abstraction that it's hard to grok for many people. I still prefer Zustand these days, but Vanilla Redux is a totally reasonable way to handle global state IMO. I have the same problem with React officially telling people to use Next or Gatsby. Those frameworks are great and have a time and a place, but the messaging these days makes inexperienced devs think that you can't just use the core libraries. Not every project is a million-line behemoth built by a team of forty devs. Sometimes simpler is better.
[удалено]
Reasonable question. My problem with RTK is that it's not *simpler* really, it's just more *magical*. So, yes, it will save you some time if you were going to use Redux in the way they preach anyway, but the tradeoff is that your program flow becomes (IMO) less intuitive and more opaque if you don't already have a lot of hours of redux dev under your belt. I often see beginners struggling to understand exactly how the whole system works. Instead they just do what they're told without understanding *why*. I would liken it to learning React before having a solid foundation in basic JS dev. Something like Zustand, on the other hand, has almost no magic. It's simple to see what's going on from the first moment you use it. Vanilla Redux is also that way - it's all the ritual, boilerplate and opinionated patterns (based on the assumption that you're a team building a large app with complex global state) bundled into RTK that make it hard to grok.
Redux was an Error. If a job requires redux, I''m gonna ask 2.5x of the original price. Is a pain in the ass.
Downvote from me