react-hands VS jotai

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!

Daishi Kato, creator of Zustand and Jotai, says there are a few things we need to support RSC serialization:

I've just published jotai-wrapper, a super tiny and simple utility library that makes using jotai even simpler. It comes from the necessity to migrate a project with react-context-slices to jotai. Both libraries share a similar API. While in react-context-slices you have the useSlice hook, in jotai you have the useAtom, useSetAtom, and useAtomValue hooks. In react-context-slices you define either React Context or Redux slices, while in jotai you define atoms. The need for the migration from the first to the second was a high memory usage by react-context-slices when using React Context slices.

Atom-based: splits states into tiny pieces of data called atoms, which can be written to and read from using React hooks. In this group, we have Recoil and Jotai.

jotai Is the signal based state manager I recommended, offering the best developer experience (in my opinion) as it eliminates the necessity to define and update a global store

Jotai 🧙‍♂️

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.

Global State Machine: Jotai (great for any state that needs to be stored globally for your application)