PSA: if you add a Service Worker to your app *but do not use it to handle top-level requests*, things *will* be slower.
-
-
Replying to @slightlylate
I've seen many teams full of smart people do exactly this and then go "why is it slower?". Uh...'cause you put another proxy in the middle.
4 replies 1 retweet 6 likes -
Replying to @slightlylate
Cannot stress this enough: Service Workers are designed to enable the offline-first architecture -- which is faster! Do not help otherwise.
4 replies 7 retweets 17 likes -
Replying to @slightlylate
offline is just one of the cases sw enables. If that is the only use case why develop something as versatile as sw?
1 reply 0 retweets 0 likes -
Replying to @everConfusedGuy @slightlylate
giving developers the power to do so much more and saying sorry sw is not designed for that is just shifting the blame.
1 reply 0 retweets 1 like -
Replying to @everConfusedGuy
: this isn't blame-shifting, it's physics. Process & thread creation take time. SWs are *intentionally* not magic
2 replies 0 retweets 0 likes -
Replying to @slightlylate @everConfusedGuy
how much SW overhead are we talking about? 100ms, 500ms?
1 reply 0 retweets 0 likes -
Replying to @vivainio
: it's system dependant; worse on slower boxes. We see SW startup in 10s-100s of ms @ 95th percentile
2 replies 0 retweets 0 likes
: ...and working to drive that down; but meta point remains
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.