… the TAG should probably give some guidance about when a CPU-bound operation takes long enough to make it promise-based. e.g. Hashes and AES handle 1MB in about 1ms, which is probably fine to block the main thread, but we also just added img.decode() because images take longer.
-
-
I think there is a clear misunderstanding here as to what these operations actually are. Twitter is not a good medium to clear this up. Let's get on a VC when I'm back at work and not dealing with a move.
-
Sure thing. Very excited to learn more about your use cases!
End of conversation
New conversation -
-
-
Feature Policy might be a way to do this for a dev-chosen set of Workers?
@iclelland We've got one for sync-xhr; would it make sense to do a unified one for all sync APIs to cover Atomics.wait(), OffscreenCanvas.commit(), and new ones in the future? -
That was to undo the mistakes of the past, it wasn't supposed to permit new sync stuff in the future. Browsers will ignore sync xhr or document.write in a bunch of situations to compensate for bad sites out there. I'd say probably better to not add new footguns.
- 1 more reply
New conversation -
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.