+1 @DavidBruant A lot of our guesses around deploying type=module (w/or/w/out Push/preload etc) will need more experimentation
-
-
What would be a good experiment? Edge has both and I have the time.
1 reply 0 retweets 8 likes -
I reckon: bundled vs module + h2 push, 3g vs wi-fi, cached vs uncached.
1 reply 0 retweets 6 likes -
Replying to @jaffathecake @matthewcp and
Also: changing a single module in the graph (send whole bundle vs. send single module)
2 replies 0 retweets 8 likes -
Replying to @domenic @jaffathecake
Imagine an update as a git fetch in a service worker. Per-module piecewise upgrade becomes feasible (and atomic).
2 replies 2 retweets 12 likes -
@cramforce The key is that the whole app needs to be staged in the cache, to eliminate the RT that diffs dev and prod2 replies 0 retweets 1 like -
Replying to @kriskowal @jaffathecake
No RT with H2 push. Regardless,
@cramforce's point is more about current implementation inefficiencies.2 replies 0 retweets 3 likes -
I do enjoy that this will bring back the dev experience of AMD to JS dev with modules in the browser.
4 replies 0 retweets 10 likes -
Replying to @cramforce @domenic and
this all rests on the assumption of the server knowing your dependency graph for an entry point
2 replies 0 retweets 1 like -
Replying to @samccone @cramforce and
h2 push at best saves you 1 RTT cost. The big win comes from shipping less & granular cache
1 reply 0 retweets 1 like
: still tho, that's an RTT in the critical path...that matters a LOT. @cramforce @domenic @kriskowal @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.