comlink

Another trick — use comlink (https://github.com/GoogleChromeLabs/comlink) to make the worker thread into essentially an async API of your local methods.

I understand, but things like https://github.com/GoogleChromeLabs/comlink enable it. Similar to how iFrames don't have access to their parent page you need a facilitator. My question is why not use a js facilitator that could work in all browsers, rather than just Chrome. I find it an interesting choice that the author decided to invest in new iFrame technology rather than existing multi-thread technology in the browser.

It's surprisingly reminiscent of Comlink[0], the Google Chrome team's library for orchestrating and messaging web workers. [0]: https://github.com/GoogleChromeLabs/comlink

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

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/manual@v1.25.0/runtime/workers#specifying-... [2] https://github.com/GoogleChromeLabs/comlink

It's not oriented specifically at state-sync'ing, but Comlink[1] comes to mind. > Comlink.wrap(endpoint) and Comlink.expose(value, endpoint?) Comlink’s goal is to make exposed values from one thread available in the other. 'expose' exposes 'value' on endpoint, where endpoint is a postMessage-like interface. 'wrap' wraps the other end of the message channel and returns a proxy. The proxy will have all properties and functions of the exposed value, but access and invocations are inherently asynchronous. This means that a function that returns a number will now return a promise for a number. Creating & exposing an EventEmitter in the main thread then proxy'ing it on each other thread ought create a reasonably similar experience to this Tangle library. The docs themselves discuss some of the extra difficulties if one is trying to proxy DOM Ev

There's overhead to a process that doesn't exist with threads. You can definitely split your work across threads in JS using Workers, ServiceWorkers and the main thread. Most apps don't take advantage of this very well though. Using a separate thread gets you the same GC benefits. There have been some attempts to make it easier to use threads on the web like the excellent Comlink library: https://github.com/GoogleChromeLabs/comlink

Also supports Node.js, service workers and iFrame communication. https://github.com/GoogleChromeLabs/comlink

Other than the built-in thread pool task scheduler, how does this differ from Comlink [1]? 1. https://github.com/GoogleChromeLabs/comlink

The problem is mostly in that all these functions are closures, and scope can’t easily be transferred. Domenic and I have been working on a proposal[1] called Blöcks to introduce transferable functions to JavaScript. In the meantime, I wrote Clooney[2] ontop of Comlink[3] that gives you almost that. [1]: https://github.com/domenic/proposal-blocks [2]: https://github.com/GoogleChromeLabs/clooney [3]: https://github.com/GoogleChromeLabs/comlink

Hey everyone, proposal author here :D Surprised to see this show up on HN _now_, since the WICG discussion[1] has been held a good while ago. The things that have been pointed out here are similar to the feedback we’ve gotten from other browser vendors. Most crucially: We might be conflating two separate improvements here. On the one hand, there’s the ergonomics feature of async-ifying remote value and on the other introducing custom worklets that can share OS threads. As a result, I have extracted the magic sauce from the tasklets polyfill into its own library “Comlink”[2] and I plan to write a couple of web apps using it to gather some perf data. With that data we can hopefully figure out if the ergonomics layer is worth standardizing. Same goes for the worklets. I’ll be using good old web workers and see how big the perf impact is. Wit