The sloppa in this article is... offending.

The obvious AI headings, pointless genned image of people (I'm starting to think islam had a point with discouraging depictions of human figures), and especially the blurry, artifacted, distractingly skeuomorphic diagram, with random wire traces going everywhere... this is a technical blog, not an investor sales pitch! Every time I see one of these, I have to double-check for a second if I'm not on some phishing SEO site!

If even Google, previously a gold standard of technical writing, is falling prey to this kind of laziness, then I have nothing to worry about -- knowing how to write without a language model in the driver's seat is gonna be a top tier skill in the future...

A damn shame too, as I've been following the progress of JXL in the standardization pipeline for a few years now and was quite interested in the historical breakdown, but all that's gonna stick with me from this is the disrespect I felt as a reader.

> In this Gemini-reconstructed scene, ...

I'm generally pretty pro-AI, but I find this icky. Of course, I wouldn't have noticed except the whiteboard drawing seemed not quite right, so I'll probably be fooled in the future.

Huge fan of JXL, but this article feels pretty AI sloppy. Not much said here, coming from the google blog I was hoping for some news about how they are pushing the format forward by introducing decoders in to Android and enabling on Chrome.

Android is the only mainstream OS that does not support JPEG XL right now.

Weird they don't name Jon Sneyers - a person pivotal in creation of JPEG XL

Here's a blog post by him: https://cloudinary.com/blog/2026-the-year-of-jpeg-xl

That's rich coming from the company that tried to kill it. The audacity...

I'm behind -- did Chrome un-remove JXL support? Google is suddenly behind it again? Why/how did they change their minds?

Can someone explain where are we at the image processing world/timeline? Why do coding tools suggest to me .avif and .webp, and the support of these lags in Windows OS and then we have things like JpegXL and Jpeg2000 or whatever others are there flying around? Why is it so hard to find our next "jpg format"?

Conveniently forgetting how they removed the jpeg-xl support from the chrome codebase despite overwhelming developer backlash that they then proceeded to ignore for over a year.

They literally tried to kill it - stating (nonsensical) reasons why it was obsolete and unneeded.

And since now the rest of the world have adopted it despite Google, they have crawled out of their slime pits praising themselves for its development with only a passing mention of cloudinary?

Sickening.

Google spearheaded this and yet their browser only has experimental support? While Safari shipped it in 2023? At least, that’s how I’m reading this.

Out of experimental when?

Mostly off topic, but why is the spec for JPEG and JPEG XL paywalled? I wouldn't call them open standards if they're not available free-of-charge to the public.

AI slop article

[flagged]

I personally think something like the qok format is a better way to go. Make something that performs well and is dirt simple to implement.