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 h

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. With that data we can hopefully figure out if we “just” need to optimize Workers or if there’s some gains that can only be reaped by the worklet approach. [1]: https://discourse.wicg.io/t/proposal-tasklets/2199 https://discourse.wicg.io/t/proposal-tasklets/2199 [2]: https://github.com/GoogleChromeLabs/comlink https://github.com/GoogleChromeLabs/comlink