Re: [w3c/ServiceWorker] Top-level await integration for ServiceWorkers running modules (#1407)

I think there's a false association that async implies slow. A large number of use cases of top-level await (or WASM modules) are likely to only be expensive on first register as things will likely be in various caches on successive loads.

I think it would be fine to just allow whatever and instead add a couple new performance entry types like `'service-worker-first-load'`/`'service-worker-successive-load'` that measures the speed that services workers loaded in response to first register/successive loads.

-- 
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/1407#issuecomment-502529934