- From: Matt Falkenhagen <notifications@github.com>
- Date: Mon, 17 Apr 2017 23:55:39 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 18 April 2017 06:56:12 UTC
cc @slightlyoff @jakearchibald Chrome is likely shipping SharedArrayBuffer soon and Chrome needs to decide whether to ship Atomics on service worker. @jeisinger points out on https://bugs.chromium.org/p/chromium/issues/detail?id=711809 that disabling Atomics means disabling WebAssembly on service worker. Are we OK with this? As I wrote on the bug, since service worker is not designed for heavy synchronous tasks, I think I'm OK with it, though I may be short-sighted here. Of course it's easier to loosen the restrictions later if needed, than to go the opposite direction. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1115#issuecomment-294705916
Received on Tuesday, 18 April 2017 06:56:12 UTC