jotai VS simpler-state

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)

The link go to a 404. There is the correct link : https://github.com/arnelenero/simpler-state

Would that be the transform function from here [1]?

I do agree too that this definitely should be a library on its own.

Anyway thanks for your work; I'll definitely check SimpleR in my project.

[1] https://github.com/arnelenero/simpler-state/blob/f6336817c9e...

Show HN: SimpleR State – simplest state management for React\ (18 comments)

Hi. There are LOTS of much more popular libs you can choose from. My library does not intend to compete as the "best" library, but it has a very specific set of goals, the topmost of which is simplicity through a minimalist API.

Everyone has different priorities when choosing a library, so I suggest going through the design goals that I highlighted in the README file, or complete documentation here:

https://simpler-state.js.org

and see if it fits what you're specifically looking for in a library.

At the end of the day, all these libraries are just React code. In that sense they differ in terms of patterns/principles behind their implementation, but maybe more importantly, in the API/syntax (which is what immediately matters to the developer using it). This is what I can confidently say that SimpleR State delivers... one of the simplest APIs you can find.

I opened a Request For Comments (here) on GitHub. Your comments and suggestions would be greatly appreciated. Feel free to drop me a comment here 👇 too.