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 …
Any story out of aggregates this large is hard to tell without lots of care, particularly when some populations are so much smaller. That said, I expect many things to be happening here at once (ctd.):
-
-
- jquery represents a much larger fraction of sites, many of which will be much older... - the previous generation of webdev viewed JS w/ more suspicion or assumed they could afford less (they were right!) - newer sites are likely to include much more active 3p bloat (ctd.)
-
- 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.)
- 3 more replies
New conversation -
-
-
If we could pull the architectural patterns we have in-page progressive/optional JS vs. full page required JS. I am sure we can guess which is going to have the lousy performance footprint. The libs correlate to approach taken & probably the approach matters more here
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.