Hacker News Reader

Provide alternative formats, making the browser autoselect. Or provide a JXL polyfill.

In either case: Have Chrome telemetry report home that "user could have 20% faster page load with JXL support".

JXL polyfill is definitely the way to go to force Chrome's hand.

It’s not going to force Google’s hand. Using a polyfill will slow page loads and adds additional fragility.

Nothing changes for Chrome users, especially sites using the <picture> element where the first supported image format is used.

It will slow page loads for Chrome and browsers not supporting it but it will be blazing fast on Safari. You keep the file size savings and high image quality.

I’m sure YouTubers and tech sites will love to do Safari vs Chrome (and Co.) content to spread the message that Chrome is inferior.

Reply on news.ycombinator.com