> That's rich coming from the company that tried to kill it
This post is written by three of the authors of the JPEG XL spec, implementors of the reference and rust implementations of libjxl, and...longtime google employees.
This post is written by three of the authors of the JPEG XL spec, implementors of the reference and rust implementations of libjxl, and...longtime google employees.
It's incontrovertible that Google did attempt to kill browser adoption of jxl at one point. Thankfully they seem to have reversed course.
The killing of JXL did push the ever-talented Jyrki to create jpegli, which was honestly a wonder.
It's really bizarre to me that this is presented as "killing the standard". Is Apple also killing mechanical keyboards and hobby electronics development because they're the only ones who don't support Web USB or Web Serial? I strongly prefer having JXL and Web USB/Serial in my browser (FF for the last 20 years), but come on. If we don't like how much power browsers have in software distribution, then maybe software distribution outside of browsers should get fixed.
* [0] https://github.com/mozilla/standards-positions/issues/522
* [1] https://github.com/mozilla/standards-positions/pull/1064
Obviously not, but they are killing as web standards the things they omit. At present for something to be standard it needs support from safari and chrome. That's just the current state of the world.
If tomorrow safari removed support for png that would effectively kill it as a web standard (assuming it didn't lead to mass revolt ofc).
Jpegli is still a hidden gem. People don't yet understand how great it is.