I love it and fully agree. Glad to know I'm not the only one. I never took to Redux and it was one reason I focused on Angular at the time. When Hooks was finally officially released, I was able to use State and Context for state management, sans-redux. The project was a great success.
So what you think which is better for state management RTK or Zustand? For example, project is complex, has users all around the world and has to be scaled.
Both are perfectly fine tools, used widely in production. I guess it boils down to personal preferences. However, if you feel the project is large enough then maybe RTK will be a better fit since Zustand is more minimalistic.
I love it and fully agree. Glad to know I'm not the only one. I never took to Redux and it was one reason I focused on Angular at the time. When Hooks was finally officially released, I was able to use State and Context for state management, sans-redux. The project was a great success.
That's a great story. I have a very similar experience. Thank you for sharing that!
Useful information! I enjoyed reading it.
In React 19, new hooks were introduced to handle loading and error states.
Nice article, Petar!
Brushings my FE skills here with your posts.
We were migrating away from redux over context to recoil. Recoil works fine but never got out of the experimental phase, so we removed it.
Today's choice is Zustand; it feels very well integrated into react and is simple to use.
Excellent article, Petar.
Thanks, Adrian! I've heard about the simplicity of Zustand. I'll have to check it out in a project definitely.
nice little article, I could use it to refresh my React knowledge.
So what you think which is better for state management RTK or Zustand? For example, project is complex, has users all around the world and has to be scaled.
Both are perfectly fine tools, used widely in production. I guess it boils down to personal preferences. However, if you feel the project is large enough then maybe RTK will be a better fit since Zustand is more minimalistic.