> - There is not enough interest from the entire ecosystem to continue experimenting with JPEG XL

Gee. Maybe there's no interest because nobody can use it yet because it's behind a feature flag.

Most likely they want to push their own "WebP" format.

If anything it would be AVIF nowadays, which is a format that all big browser vendors stand behind, including Apple and Google

WebP2 also got "demoted" (https://chromium.googlesource.com/codecs/libwebp2/+/1251ca74...):

    -WebP 2 is the successor of the WebP image format, currently in development. It
    -is not ready for general use, and the format is not finalized so changes to the
    -library can break compatibility with images encoded with previous versions. \
    -USE AT YOU OWN RISK!
    +WebP 2 is an experimental image codec based on WebP. WebP 2 will not be released
    +as an image format but is used as a playground for image compression
    +experiments.

I dont see why its so odd. Looks like it was behind a feature flag. I imagine the time came where someone had to make a go/no-go call, and they decided no-go.

It wouldnt make sense to keep it as a feature flag forever, and once it is not a feature flag it becomes much harder to backout.

> It wouldnt make sense to keep it as a feature flag forever, and once it is not a feature flag it becomes much harder to backout

They didn't struggle with removing H2 PUSH though.

I mean, you're still talking about it, now, much later. If it was really no struggle people would have forgot about it at this point.

H2 push is also something that degrades much more gracefully if missing compared to an image codec.

Nonetheless, people haved removed image codecs before (rip XBM). Harder is not the same as impossible.

True, because I saw how it was just being added to software/frameworks. Some parts of the web move slower than Google expects, I have a feeling.