legend-state VS react-hands

There is not much to refactor in this simple example, but if we look closer to the the legend app state lib, we can see that set can take a callback with the previous state as parameter

For signals, Signia or Legend State.

I'd love to know what you think, and I'm also happy to answer any general JavaScript performance questions if you want since I've gone very deep into optimizing . See the GitHub: https://github.com/LegendApp/legend-state

After almost a year of development and iterating, we just released Legend-State 1.0. It's the fastest React state library and is very easy to use, based on Observables (Signals) with fine-grained reactivity and built-in persistence.

I'd love to know what you think, and I'm also happy to answer any general JavaScript performance questions if you want since I've gone very deep into optimizing .

https://github.com/LegendApp/legend-state

We do plan on adding a table view, and we've designed out a general idea of how it would work. And I'm very excited about it! But I'm not sure exactly when we'll start on it. Right now we're finalizing a new state/sync system (in open source at https://github.com/LegendApp/legend-state), then we'll add support for Markdown files, then a very cool new feature we're still exploring. I think you could expect sometime early next year we'll start working on expanding the view modes (but it's all still fluid so no promises!).

Legend-state - https://legendapp.com/open-source/state/

Legend-State is good.

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!