comlink VS react-easy-state

Feels like taking a general Comlink-like system & making it more component oriented. Good ideas. https://github.com/GoogleChromeLabs/comlink

React UI Framework: https://ant.design/ Reactive: https://www.learnrxjs.io/ Workers: https://github.com/GoogleChromeLabs/comlink Graphics: https://www.pixijs.com/

Reminds me of Comlink

Now that we have a way to create PDF files, we can create a web worker to run the renderPDF function in a separate thread. Here’s an example of a web worker that uses comlink to expose the renderPDF function as an asynchronous function:

To streamline the process of configuring the Service Worker and simplify communication between the app and the Service Worker, we will be using the comlink library.

While there's no realistic way to provide a security boundary between JavaScript modules, Workers are a possibility [1].

The code with the more restricted set of permissions must run in the Worker. That code then communicates with the rest of your app through postMessage / SharedArrayBuffer, perhaps using ComLink [2].

[1] https://deno.land/[email protected]/runtime/workers#specifying-...

[2] https://github.com/GoogleChromeLabs/comlink

The worker API is very simple, you would post a message to the worker. The worker would have the code to process and reply back with the results to the listeners. To make it even easier Google has created the comlink library.

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