One camp tells me the current/future is fast devices, crappy network. Build offline first (bigger JS app).
Another camp tells me network is fine, devices are slow. Ship less JS, don’t worry about the network, worry about parse/eval time.
Mutually exclusive optimizations 
-
-
Replying to @ryanflorence
I bet
@addyo and@pbakaus have some useful clarity here. I believe the ideal is to ship what's needed to make the first route interactive first, and then load the rest in the background.2 replies 0 retweets 0 likes -
I get your point but these are not mutually exclusive. The less JS the better, like
@appsforartists pointed out. Service Worker APIs are high level enough to write offline first code in hundreds instead of thousands of lines, from my personal experiences.@slightlylate1 reply 0 retweets 3 likes -
Replying to @pbakaus @appsforartists and
BTW, compressing these futures into a single point is not-even-wrong. Networks and devices are improving, but the *spread* in the range of both is widening.
1 reply 0 retweets 4 likes -
Replying to @slightlylate @pbakaus and
We used to have fewer users with more similar devices on more homogenous networks. Analogy: avg(5, 10, 15) == avg(1, 1, 1, 1, 3, 5, 5, 5, 7, 71)
1 reply 0 retweets 3 likes -
Replying to @slightlylate @pbakaus and
The average can stay the same while the situation changes dramatically.
1 reply 0 retweets 1 like -
Replying to @slightlylate @pbakaus and
That's what we're seeing today. If you only care to serve wealthy users, then CPU is free-ish. If you care about the *most* users, then CPU is stagnant and poor networks are improving (unevenly).
1 reply 0 retweets 3 likes
For almost no set of users, however, are desktop-holdover perf budgets a reasonable baseline.
-
-
Replying to @slightlylate @pbakaus and
I feel like I activated the
@ChromiumDev batsignal.0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.