I’d pay good money to see what, precisely, is in those bundles. I’m guessing the unusably slow media sites that take many seconds to load are not so because React is powering their view layer
-
-
I think even Alex will admit that biggest offenders are media sites and it's not their bundles but the number of scripts for ad networks they load :(
1 reply 0 retweets 3 likes -
I admit no such thing. 1pJS went from being "meh, OK" to an absolute, ship-sinking disaster in the past 5 or so years. I focus on it as a result.
2 replies 0 retweets 3 likes -
Show us. Remove the names to protect the innocent, then show us the numbers. Please. Which libraries are adding up to what bundle sizes?
1 reply 0 retweets 0 likes -
You know the names.
2 replies 0 retweets 0 likes -
Replying to @slightlylate @AdamRackis and
To back Alex up, 1P script costs are a daily issue we see. That's not to say 3P can't also tank perf, but we'd be lucky if that was the only problem. Challenge is whatever fw you pick, it's _too_ easy to install a spectrum of other libs that bloat your bundle. Need perf budgets.
2 replies 0 retweets 18 likes -
Replying to @addyosmani @slightlylate and
Are people importing things badly, and pulling in all of lodash, d3, react-bootstrap, etc? Or are people really just installing a hot dozen un-needed js libraries. Some actual use cases would help a great deal here.
1 reply 0 retweets 2 likes -
Replying to @AdamRackis @slightlylate and
Things tanking experiences: 1. Shipping monolithic bundles w/o code-splitting 2. Including all of popular libraries vs. what you need (full UI libraries, lodash, d3, moment.js + locales etc). 3. Shipping unnecessary polyfills for target browsers 4. Duplicate (+oversized) libs
3 replies 9 retweets 46 likes -
Replying to @addyosmani @slightlylate and
Geez - that's depressing. We were code splitting BEFORE requireJS. There's just no excuse at this point. And duplicated libraries?! Are people not inspecting their apps with the bundle analyzer for fishy output? The tooling's never been better, but devs are still phoning it in.
1 reply 0 retweets 1 like -
Replying to @AdamRackis @slightlylate and
Most front-end developers I've engaged with don't know that they need to use a bundle analyzer to discover fishy JS output. I wish modern web tooling (DevTools, F/W CLIs) gave you better guard-rails to avoid this stuff, or better highlighted when you have issues & the next steps
1 reply 1 retweet 14 likes
Indeed; I'm pursuing this point with our tools folks now. The knowledge gap is vast.
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.