Re: [w3c/ServiceWorker] Soft Update seems way to aggressive (#1250)

Since my previous comment wasn't clear to some people who reached out to me, I mean that **service workers being cached has been the problem for our users** (not the opposite!). They couldn’t deploy urgent fixes and this was extremely hard to debug because of Chrome caching the service worker. Create React App users are pretty representative of the general web developer community given the popularity of React so I wouldn’t discount their experiences.

You can read [this thread](https://github.com/facebookincubator/create-react-app/issues/2398) (one of our most voted and commented issues) to gauge the developer sentiment about service workers, the resistance in large being driven by this behavior, and that most people learn about it too late when it bites them.

If this problem didn’t exist in Chrome, maybe we’d keep them in, but at this point our users have made it clear that the deployment pitfalls are too painful to them. If Safari adopts this behavior, I think it will bump into the same issues, and potentially hurt service worker adoption. I might be wrong though.

-- 
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/1250#issuecomment-358056346