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]
It’s slowly marching along with the reimplementation of its reference decoder in rust. That should hopefully satisfy google and mozilla’s demands and get them to adopt it in their browsers.
Never understood why jepgXL didn’t win out
Because Google didn’t invent it, and Google decides what does and doesn’t get added to the Internet.
Google were literally one of the three organisations who worked on the standard, and the top contributor to the reference implementation works there.
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.
- https://en.wikipedia.org/wiki/JPEG_XL
It’s different people who develop and who decide.
It’s slowly marching along with the reimplementation of its reference decoder in rust. That should hopefully satisfy google and mozilla’s demands and get them to adopt it in their browsers.