One way to think about the tables in @tkadlec's excellent post is pre-vs-post NPM: having made it much easier to include code at dev time, responsible frameworks and teams must work that much hard to exclude it from taxing users at runtime.https://twitter.com/davatron5000/status/1252637544149323776 …
-
-
- npm has made it much easier to pull in larger deps - the disparity between high-and-low-end perf has widened, meaning things that are slow don't *feel* slow at dev time - the distributional effects of survivorship may keep slower tools on the margins (ctd.)
-
That last point is particularly confounding: correlation and causality are hard to suss out, but one theory we could test is "are sites built with [slow 'modern' tools] less likely to succeed in the market?". You could ask lots of proxy questions to get a handle on it.
- 2 more replies
New conversation -
-
-
That's fair, too. jQuery's peak "new usage" was during a different time before people were like, "Fuck it, 5g is a thing now!"
Thanks. 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.