Re:Chrome Never-Slow Mode Prototype
by slightlyoff on Wednesday February 06, 2019 @03:01AM
(#19093499)
Hey, author of the patch here.
The restrictions are wire size. `bootstrap.min.js` is ~10KiB on the wire, which means it comfortably fits (as do jQuery, most analytics packages, etc.).
That said, the prototype does break a lot of the web, but that's not a crisis. The intent isn't to have this rolled out everywhere against unwitting content, but rather (like TLS), to let developers opt-in to a single set of rules when they see value. There are also places (e.g. PWAs) where the browser-imposed quality bar needs to be high. Blocking PWA install for sites that don't send the opt-in header seems like a reasonable place to start.
And moment.js is 68 and luxon 64.
Re:Chrome Never-Slow Mode Prototype
by TheCoelacanth on Tuesday February 05, 2019 @10:04PM
(#19092342)
Moment.js is 16.7k. Moment.js plus locale data for every single locale in the world is 68k. There is no justifiable reason to ever load every single locale in the world at once except for a few extremely niche cases. Real world use cases typically need one locale at a time, occasionally two or three, never hundreds.
Luxon, I believe, is a similar story.
For example, non-minified bootstrap.js is more than that. Just as a data point.
This will break a bunch of the web. I'll be curious to see how this gets worked out as the work progresses.