There are folks who want you to believe it isn't a problem that "modern" frontend starts with 35KiB of JS and scales obscenely from there. The mobile web ecosystem is collapsing because of JS emissions. We can't afford denial any more.https://twitter.com/FronteersConf/status/1185099012128595970 …
-
-
Yep! At Facebook we've been using this pattern since 2010 via bigpipe and carried it over into the new Facebook as well. (https://www.youtube.com/watch?v=WxPtYJRjLL0 …) But when we display things we still need JS to ensure that it's interactive enough to show something basic while the next view load.
-
Yep! But the cost of that abstraction, today, shouldn't be 35KiB; certainly not for most users who have access to modern JS/DOM. Getting to a reasonable per-interaction cost means economising at every level.
End of conversation
New conversation -
-
-
Do you know of the state of benchmarks comparing bundling to non-bundling using the platform's native capabilities? Last I saw was like 1-3 years ago, Khan Academy I think did some research, and the conclusions were that bundling was still more performant
-
If new benchmarks don't exist, we should create some. Webpack or Parcel or Rollup with file splitting versus straight platform tools with no bundling. It would be nice to have a cannonical example site or set of sites where the benchmarks could be run in real time like Lighthouse
- 1 more reply
New conversation -
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.