If you don’t care about prolific side-channels... and mountains of extra complexity and attack surface.
-
-
Have you weighed in on the OffscreenCanvas.commit() questions? They're designing around a Wasm model that never yields. Now, it'd be totally possible to provide a way to read Promises values synchronously, so that we don't need to dupicate every API.
-
I'm deeply uncomfortable about that design. The more I look, the more it worries me. Will discuss with those folks shortly.
- 20 more replies
New conversation -
-
-
You’re skeptical of blocking on non-main-thread?
-
Yes, particularly for generic APIs. There's a pretty bad ice-9 effect
- 1 more reply
New conversation -
-
-
I think we just did it wrong back then. If instead we had a few simple primitives for blocking the worker thread on completion of a task (e.g., wait for promise / wait for first of N promises), we'd have a better result. It'd be like what other OSes provide.
-
We are anyways enabling people to do all of this themselves with the addition of SharedArrayBuffer and Atomics.wait.
End of conversation
New conversation -
-
-
I am hugely skeptical of wasm, period.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.