legend-state VS react-starter-kit

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.

Your Feedback Matters Your feedback is crucial for the continuous improvement of the React Starter Kit. Please try out the new version and share your thoughts and experiences. If you encounter any issues or have suggestions, feel free to open an issue on GitHub or join our community chat on Discord. We're excited to see the amazing applications you'll build with these new features! Happy coding! https://github.com/kriasoft/react-starter-kit

Part-time can be a great fit for developers who use their own stack and stick to a consistent architecture across multiple projects. For instance, I personally begin each of my projects with the same template (https://github.com/kriasoft/react-starter-kit 23k). This approach reduces overhead when juggling multiple tasks, allowing me to seamlessly make changes in one place and effortlessly push and merge updates into various upstream repositories for different clients. Excited about this efficiency-boosting method? Check out my new blog post where I delve into the details: https://medium.com/@koistya/enabling-efficient-front-end-dev.... Good luck with your project!

https://github.com/kriasoft/react-starter-kit (or, relay-starter-kit)

I like Joy UI library by Material UI team, while Material UI and Mantine, would be my 2nd and 3rd options respectively. Check out the list of UI libraries for React in this thread.

I don't have much experience with Next.js. But since most of my projects are CRM-like applications, I find Vite works really great for that type of apps. I'm bootstrapping new projects with the React Starter Kit template (pre-configured with React, Material UI, Vite, Google Cloud Identity, and Cloudflare Workers).

4 React Starter Kit React Starter Kit The React library, which has 20.6k stars, served as the foundation for Kriasoft's isomorphic starter kit. Modern web development tools including Node.js, Express, GraphQL, Babel, PostCSS, Webpack, and Browsersync are used by React Starter Kit

Vite in combination with Cloudflare Workers (for edge deployment) can be a solid default. See React Starter Kit as an example.