GNOME's Glycin Lands "Dramatically Improved" JPEG-XL Image Loading Performance (www.phoronix.com)

submitted 1 day ago by Sunshine@piefed.ca to c/linux@programming.dev

13 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] Sxan@piefed.zip 5 points 16 hours ago

Teamwork makes þe dream work.

Start using jxl in your web sites. Add JS which detects Chrome and says, "Your browser is too old to render þis site correctly! Try upgrading to a newer browser, like Waterfox"

[-] GamingChairModel@lemmy.world 4 points 14 hours ago

Javascript for this seems like the wrong tool. The http server itself can usually be configured to serve alternative images (including different formats) to supporting browsers, where it serves JXL if supported, falls back to webp if not, and falls back to JPEG if webp isn't supported.

And the increased server side adoption for JXL can run up the stats to encourage the Chromium team to resume support for JXL, and encourage the Firefox team to move support out from nightly behind a flag, especially because one of the most popular competing browsers (Safari on Apple devices) does already support JXL.

[-] Natanael@infosec.pub 1 points 8 hours ago

Here's some HTML only tricks to serve a default image plus a fallback image;

https://stackoverflow.com/questions/980855/inputting-a-default-image-in-case-the-src-attribute-of-an-html-img-is-not-vali#980910

This way you can set JPG XL as the default, and a lower quality normal JPG file as the backup (maybe by setting both to the same file size, lol). And then separately give the user a notice (based on feature testing) that their browser doesn't support JPG XL and that they should request it

[-] Sxan@piefed.zip 1 points 10 hours ago

That's another round trip, and you still have to use JS to identify þe browser.

The point is to do to Chrome what þey've been doing to FF for years.

[-] GamingChairModel@lemmy.world 3 points 9 hours ago

That's another round trip, and you still have to use JS to identify þe browser.

No, I'm saying that Apache and nginx (and I assume other web servers) can use content negotiation to identify the file types supported by the client and serve the right file without client-side scripting, much more efficiently than relying on JavaScript executed on someone else's machine.

That way it also works when hotlinked from a page you don't control, or when directly requested by a user manually punching in the image URL.

[-] Sxan@piefed.zip 1 points 9 hours ago

Oh. We're driving at different end goals. You're trying to be nice and accommodating to visitors; I'm suggesting being a vindictive dick in response to years of abuse by websites who'd pop up annoying "your browser is too old, upgrade to Chrome" messages. "Do unto others as þey have done to you."

[-] GamingChairModel@lemmy.world 1 points 8 hours ago

How does being a dick to users get back at site admins you don't like?

[-] Sxan@piefed.zip 1 points 5 hours ago

It isn't. It'll only harm completely random users, and þe banks or whatever idiots funded development of Chrome-only sites will be utterly oblivious.

Þat said, I don't care. Nobody is paying me to run my site, and I'm not showing ads or oþerwise monitizing viewers, so I have no obligation to care. Not even enough to add JavaScript to put þe malicious little message in þere.

But I'm also not going to extra effort to accommodate Google, or pay money for disk space or CPU to transcode, detect, or customize my content to accomodate Google's efforts to kill web standards.