Wherein @jaffathecake cogently lays out (in the comments) the _real_ speed advantage for Service Workers: https://plus.sandbox.google.com/+IlyaGrigorik/posts/WPZsWr4QGqR …
-
-
Replying to @slightlylate
@slightlylate@jaffathecake still doable with existing tools (see reply)... albeit, yes, with a lot more pain :-)1 reply 0 retweets 1 like -
Replying to @igrigorik
@slightlylate@jaffathecake just to be clear, SW will make this way simpler.. and practically deployable - I'm a fan.2 replies 0 retweets 0 likes -
Replying to @igrigorik
@igrigorik : the thing@jaffathecake points out where you fetch *DIFFERENT* content if you have the shell isn't possible today.1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@jaffathecake not sure I follow, as in: show stale content vs block on the fetch? you can do that today with XHR+localstorage.1 reply 0 retweets 1 like -
Replying to @igrigorik
@igrigorik : and then you can't handle non-JS-using clients. SUPER special-case-y. /cc@jaffathecake1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@jaffathecake yep, there is a special circle of hell for that one.. SW would be of no help there either.1 reply 0 retweets 0 likes
@igrigorik : you can progressively enhance with the SW. No-js friendly by default.
/cc @jaffathecake
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.