comlink VS solid

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.

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.