Users with the fastest devices and networks -- which includes ~all developers and business decision makers -- are leaning into technologies (JS) that, by their very nature, are decreasing the reach and usability of their services for users outside the bubble.
-
Show this thread
-
These devs & managers benefit from the Performance Inequality Gap in many (often indirect) ways, but not nearly as much as their now-margninalized users (and their businesses) lose.
1 reply 1 retweet 7 likesShow this thread -
JS-first moves services away from a Pareto frontier. If they had continued to produce their services with ~mostly HTML, they'd maximize reach at a cost to richness. By moving it to ~mostly JS, they *think* they're keeping reach -- it's on the web -- but that's not what happens.
2 replies 3 retweets 8 likesShow this thread -
If each KB of JS had the same win in richness as the reduction in reach, they'd be at the frontier, just at a different location. Instead, the marginal KB added by Babel/Webpack/NPM/React/etc. is *almost never* an equivalent win in richness as the reduction in reach.
1 reply 1 retweet 8 likesShow this thread -
The cumulative impact is that the web reaches fewer people...and that's not a crisis for folks inside the high-performance bubble because they've got theirs.
1 reply 2 retweets 5 likesShow this thread -
I got distracted by this when thinking through teams I've worked on/with which had slow DBs and servers vs. bloated frontends. Why does the former usually get fixed but not the latter?
1 reply 2 retweets 5 likesShow this thread -
Answer? Slow DBs are equally slow for everyone. The server boundary is a *class solidarity boundary*.
1 reply 3 retweets 16 likesShow this thread -
JS has broken the "we're all in it together" aspect of frontend.
2 replies 2 retweets 12 likesShow this thread -
Replying to @slightlylate
Is it really JS or is it the devs & management that put the priority on it above other aspects.
1 reply 0 retweets 1 like -
Replying to @pgrucza
I blame managers, but the thing that proximately makes sites inaccessibly slow is the JS. Empowered TLs can sometimes fix.
1 reply 0 retweets 0 likes
But it's JS's unique predation on client CPUs that creates the disconnect and enables the bubble to become a hard wall. So JS (sent to the client) is uniquely problematic.
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.