Re: [w3c/ServiceWorker] When should "imported scripts updated flag" be unset? (#1021)

Personally I'm inclined to keep importScripts() as a sync script eval thing only right now.  Reasons:

1. Async importScripts() is a complication for an already complicated piece of code.
2. Its unclear how much devs will feel they need to risk janking startup of the SW which is off the main thread.  I personally have not seen people clamoring for this yet.
3. Browsers can minimize the impact by storing pre-compiled js for offlined scripts.  So the real impact is mainly felt at update/install time.
4. Nested dedicated workers would allow developers to explicitly move work (including eval of heavy scripts) out of the service worker into a separate thread.  I think this is something we want for other use cases and it could potentially solve this use case as well.
5. Its easier to allow install event importScripts() later if we get a lot of feedback from devs that its needed.

-- 
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/1021#issuecomment-265845754