legend-state VS pullstate

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.

PullState - https://lostpebble.github.io/pullstate/

Pullstate. It's a lot like svelte's store.

And automatically, any components using uiStateStore.useState and watching the isSidebarOpen property will get updated, exactly the same as the normal useState hook - just shared.

It's so dead simple and has made complex app-building so much easier for me.

The one caveat is that if I have a component with many handlers, e.g. onClick, onMouseMove, onContextMenu, onMouseLeave, etc (and in some cases I do), components can get bloated. I haven't found a fix to that yet. But that's more an inherent issue with react than anything to do with state management.

[1] https://github.com/lostpebble/pullstate

Sounds like you're on the right track. React is very hire-able. Try out multiple store systems. The big one is react + redux. Then after you have some experience with that, try a simpler one like pullstate.

You could try out pullstate - its basically just global objects which you can mutate and which automatically update your state over your entire app, for whichever parts you have "pulled" the state into.