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

Sorry for the slow response, have been on holiday. Thanks @jakearchibald for capturing (accurately) our pub conversation.

My largest concern about the declarative proposal here is that it's a high-level, open-ended design space which is something we've decided in the past not to attack without lots of evidence of need. At some level, I think these proposals are compatible. You can imagine the high-level thing being implemented in terms of the low-level sketch I outlined without much difficulty.

While I accept the critique that this may be scenario solving to some degree, we've had multiple customers ask for something that's effectively this and we know that multi-process browsers will be architecturally constrained in ways that make the PlzNavigate decision common.

The alternative that preserves our low-level bias in design is to simply block all navigations that have SWs on them on renderer startup and defeat PlzNavigate (and equivalents). I'm not sure this is tenable, so I'd like to see something small that's low-level in this area while we design the high-level route system.

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