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

It's also not just about control. I think the problem is “it works until it doesn’t”.

* it's often not clear *where* the issue is (not obvious crashes are caused by caching since they end up very confusing and unreproducible on new builds)
* people are used to *deploying* being the immediate solution, and it’s very hard to undo years of learning that it’s enough to get out a fix
* Chrome doesn’t give any immediate indication that something is served from cache

So by the time they *discover* it was due to the cache they are already frustrated enough with this technology that they never want this experience again.

Just read [this report](https://www.reddit.com/r/javascript/comments/6dwbig/react_running_even_after_everything_removed/):

>It's at this point I decide I'll continue this another night. So I close cmd. I turn my pc off. Later I turn it back on, and go to localhost for another purpose. And lo and behold what do I find, this ****ing default react app running. I dont even understand how, there's no active process. I google the *** out of it to find out why and how this react app might be running on localhost:8080 when I'm not actively doing anything. Cant find ***.
>
>So I delete the files installed by c-r-a. It's still running on localhost. I uninstall node and search my whole pc for any of these default files and find nothing... IT'S STILL RUNNING.
>
>Node is gone. React is gone. The default files from create-react-app are gone. How can this react app still possibly be running on localhost ?!!?!?!?!?!?!?!

And that’s on a *local machine*. Imagine what a nightmare it is to debug something like this when it only happens to some users *in production*.

-- 
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-358286884