Over the past few months, we’ve had some productive conversations with the JPEG-XL team at Google Research around the future of the format in Firefox. Our primary concern has long been the increase...
Developed by the google research time. Pretty ironic
This is pretty huge. With both Apple and Firefox supporting it, chrome will be the only major holdout, and it could put more pressure on them to add support.
The Chromium team is made up of developers like James Zern (the one who closed jpegxl’s inclusion as obsolete(won’t fix) twice) who are active developers of Avif and Webp2. Both of those formats really suck and have a lot of problems they just handwave away. Avif is constantly breaking compatability and has some bit depth jank that breaks how it renders.
This is pretty huge. With both Apple and Firefox supporting it, chrome will be the only major holdout, and it could put more pressure on them to add support.
So despite this being developed by Google, they are not putting it in chrome? That’s dumb.
The Chromium team is made up of developers like James Zern (the one who closed jpegxl’s inclusion as obsolete(won’t fix) twice) who are active developers of Avif and Webp2. Both of those formats really suck and have a lot of problems they just handwave away. Avif is constantly breaking compatability and has some bit depth jank that breaks how it renders.
Definitely a conflict of interest… >:/