zedux VS react-hands

Atomic libs include Recoil, Jotai, and the one I maintain: Zedux. Zedux especially was designed to work well with sockets and RxJS observables and has been getting some traction recently, so of course I recommend checking it out. Feel free to hmu with any questions.

This new tool started driving our production apps in early 2021 and has been a lifesaver in the extremes of complexity. 2 years later, we have finally open-sourced this tool as "Zedux".

Zedux is a hybrid tool similar to RTK + RTKQ but with first-class DI support.

For atoms, Jotai or Zedux

Zedux is a new up-and-coming hybrid tool similar to RTK + RTK Query but with atoms

Atomic libraries like Recoil, Jotai, and Zedux specialize in expressing these dependencies clearly, giving you insight into your dependency graph and offering tools like evaluation tracing, time travel, and DI overrides to improve testability and discoverability of your code.

I'd recommend a powerful state management library for something like this, especially one that gives you full control over async flow outside React. Here's a codesandbox using Zedux to demonstrate sending 4 buffered requests per minute.

After Zustand, if you need anything more, I'd either go back to Redux or learn Jotai, an atomic library that's a little more powerful than Zustand. Atoms are a little more advanced, so I wouldn't start there. Though (full disclosure) I am the author of another atomic library that is aiming to make atoms simpler to learn and use. Someday we'll get there, but for now I'd say Zustand is the best place to start.

Source: I'm the creator of Zedux, a lib that we just publicly released a few days ago and drives lots of highly-volatile state like this in our apps. If you need a powerful state manager designed to work at scale with fast-moving state streamed over websockets (SSEs work too), it might be worth looking into. Cheers!

GitHub

Oh man I have checked out your library and loved it, and I had also made a similar library: https://github.com/javaScriptKampala/react-hands a last month or so, but now all this time I plan to rewrite all of it to better after digging more into the state management land and learning about what other big players are doing and why, one thing I still don't like about existing solutions though, they don't seem react-ish to a react developer, they seem very abstract and follow wired patterns, so now am like what if we make a library that is doing all the crazy things to manage state efficiently under the hood, but on surface behaves and has a similar pattern to useState or react hooks that to a react dev it feels so natural? And checking out your library, it seems it is what I wanted to create just with a few differences, I got some even interesting ideas on this, so how can we team up?

Does anyone think react can handle most state management issues? As today's apps are usually server data or server cache intensive than app state and hat has given more rise to libs like react query? Anyways I think react can really handle app state of 99% of the time, hence am building some state management library based on react hooks instead, the end result is a simpler and familiar thing than most of these wiredo state managers that need the dev to learn a ton of concepts, check it here: https://github.com/javaScriptKampala/react-hands and give honest feedback, first release for now by the way, don't expect too much, but much coming in next release!