react-easy-state VS solid

I've really enjoyed react-easy-state

For state, I love to use React Easy State.

react-easy-state was very easy.

If you want to try something a bit different with regards to state management, you can try: https://github.com/RisingStack/react-easy-state

Nope, react-easy-state is much easier: https://github.com/RisingStack/react-easy-state

I personally prefer to work with react-easy-state instead of using Redux or even the built-in state management in React.

Just started using react-easy-state in a project, and I have to say I love it. In the past, I used Redux/RTK for global state management, along with Redux Thunk or Redux Saga for side effects. In contrast, react-easy-state is easy and requires so much less boilerplate to setup and worry about. I’m fully comfortable using Redux in apps and have done it plenty of times, but I love how react-easy-state just works. It’s amazing being able to mutate the state from anywhere, inside and outside of components, and have it immediately reflected by components, without installing any plugins and having complex config files.

I am a big fan of react-easy-state, which uses proxies to automatically trigger re-renders when you mutate any state that the component depends on. It's a bit of a different way of using state management compared to typical immutable state examples, but it allows for some very straightforward code without much boilerplate around it.

The app for people to submit orders (drinks-user) is just a form and to manage state, I'm using React-easy-state

The strength of V-DOM definitely doesn't lay in performance. It made it easier for developers to write more maintainable interactive UI. Other than that I'd rather think of it as a compromise. Fortunately, frontend web dev continuously progresses and there are initiatives like https://github.com/ryansolid/solid which focus on compilation-time diffing.

You see I work 12 hours a day. 8 hours of that is my professional job where I am a developer on the Marko core team at eBay. Then after some much-needed time with my family, my second job starts where I am core maintainer of the under-the-radar hot new reactive framework Solid.

They’ve been well received, and the core ideas behind them have inspired the likes of Vue’s Composition API and a big part of Solid’s API.

After discovering solid js, I wondered how feasible it would be to write such a framework in Rust. After two days of hacking around, here is the result!

After discovering solid js, I wondered how feasible it would be to write such a framework in Rust. After two days of hacking around, here is the result!

Solidjs UI library uses Proxies in order to make state reactive https://github.com/ryansolid/solid

[0] https://github.com/ryansolid/solid#the-gist

The key thing to understand though is this is not a React-only approach. I make heavy use of this pattern in my Solid projects as it makes a really nice isomorphic solution and works really well with the next topic...

The main ones that I'm referring to have proxy implementations along with their basic signal atoms. MobX's `observable`, Vue's `reactive`, Solid's `state` all are reactive proxies that properly handle subscriptions.