this post was submitted on 20 Sep 2025
615 points (82.7% liked)

Programmer Humor

26628 readers
1722 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] hperrin@lemmy.ca 24 points 1 week ago (1 children)

Because Google didn’t invent it, and Google decides what does and doesn’t get added to the Internet.

[–] lengau@midwest.social 11 points 1 week ago (2 children)

Google were literally one of the three organisations who worked on the standard, and the top contributor to the reference implementation works there.

[–] hperrin@lemmy.ca 14 points 1 week ago* (last edited 1 week ago) (1 children)

And then they killed it. It was Google pulling support in Chrome that killed JPEG-XL’s momentum.

It was the Joint Picture Experts Group that invented it, so Google had no ownership over it, unlike WebP.

Google's stance on JPEG XL is ambiguous, as it has contributed to the format but refrained from shipping an implementation of it in its browser. Support in Chromium and Chromeweb browsers was introduced for testing April 1, 2021[29] and removed on December 9, 2022 – with support removed in version 110.[30][31]The Chrome team cited a lack of interest from the ecosystem, insufficient improvements, and a wish to focus on improving existing formats as reasons for removing JPEG XL support.[29][32][30]

- https://en.wikipedia.org/wiki/JPEG_XL

[–] GamingChairModel@lemmy.world 5 points 1 week ago (1 children)

It was the Joint Picture Experts Group that invented it, so Google had no ownership over it, unlike WebP.

No, JPEG called for submission of proposals to define the new standard, and Google submitted its own PIK format, which provided much of the basis for what would become the JXL standard (the other primary contribution being Cloudinary's FUIF).

Ultimately, I think most of the discussion around browser support thinks too small. Image formats are used for web display, sure, but they're also used for so many other things. Digital imaging is used in medicine (where TIFF dominates), print, photography, video, etc.

I'm excited about JPEG XL as a replacement for TIFF and raw photography sensor data, including for printing and medical imaging. WebP, AVIF, HEIF, etc. really are only aiming for replacing web distributed images on a screen.

[–] hperrin@lemmy.ca 2 points 1 week ago* (last edited 1 week ago)

So Google contributed to it, but ultimately didn’t invent it and doesn’t own it. In other words, what I said.

As opposed to WebP, which not only do they own, they also own several patents for that cover the entire bitstream. They offer a patent license that is conditional on not suing them. So they basically own and control WebP entirely. They do not own, nor do they control, JPEG-XL. Google owns patents that cover a portion of JPEG-XL, but don’t have full control.

[–] kilgore_trout@feddit.it 6 points 1 week ago

It's different people who develop and who decide.