Re: [w3c/ServiceWorker] [Feature request] Allow keeping service worker alive (#1558)

It seems to me there's an irony here: the browser understandably wants to terminate the SW where possible to save resources, but in this case dealing with that requires writing potentially large amounts of data to storage. Isn't keeping the SW alive the less resource intensive option?

-- 
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/1558#issuecomment-748055375