Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920)

Going to tackle this in two replies, one addressing the problem & another addressing the proposed solution - because I don't think they match up too well right now.

Back when we started work on SW there were calls for higher level APIs, manifests and such, because SW may present performance issues, and your response to that was roughly "We shouldn't try and solve performance problems until we know we have them, and what shape & size they are". This is still a good plan.

I want us to present solid data here that shows the size & shape of the problem, and I want other vendors to verify that SW startup is the bottleneck here, and not something specific to Chrome.

There are multiple ways to solve this problem, and the way to pick the best solution is for us all to have good visibility into the issue.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/920#issuecomment-228987668