3 ms·

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

by rowbin 4mo ago

rowbin 4mo ago
> Safari (2023) led among major browsers, while Firefox and Chrome currently maintain experimental support.
- Gigachad 4mo ago
  Maintain in a sense. Google introduced it in Chrome as an experimental flag, then removed it with no real explanation, and only just brought it back.
  - halapro 4mo ago
    Which it makes perfect since this it's the same company which "deprecated" MP4 support a long while ago in an effort to push to WebM.
    - ksec 4mo ago
      Thank You I have nearly forgotten about that. At one point I was worried they might even remove AAC-LC support.
- spartanatreyu 4mo ago
  Yeah, but they left out that Chrome removed their own support for JPEG XL saying no one in the industry was in favour of it despite everyone seeing it was the future screaming for it and building support for it into their own products. Chrome's blink was the only major browser engine not supporting it and that prevented it from becoming a web standard and they refused to acknowledge they were wrong. Chrome only backtracked once jpeg-xl was subsumed into the PDF standard because if Chrome did not support jpeg-xl, they would by extension also not be supporting pdf.
  - Gigachad 4mo ago
    jpeg xl is also now used for the latest version of the DNG raw image format, and the iphone now encodes raw images as jpeg xl in DNG. It's so clearly the future for photography that Google is holding back. Apple surprisingly has been the first with full support everywhere in their OSs and in Safari.
    - Caspy7 4mo ago
      Safari is currently lacking animation and progressive decoding - still ahead of everyone else currently. Looks like by the end of the year we can expect Chrome and Firefox support.
    - ksec 4mo ago
      I just wanted to add the decision for JXL inside DNG was well known even before it happened and Chrome still said no. Adobe and Intel along with plenty of other players in the industry screams this is so good they are all adding support. But still Google said no. And to make matter worst the publish the worst comparison document and benchmarks for AVIF against JXL.
theturtle 4mo ago
[dead]
magicalist 4mo ago
> 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.
- orbital-decay 4mo ago
  From what I can tell, it's written by Gemini
  - deleted 4mo ago
    [deleted]
- fc417fc802 4mo ago
  You say that as though Google isn't notorious for killing their own successful and well received products for seemingly no reason. It's incontrovertible that Google did attempt to kill browser adoption of jxl at one point. Thankfully they seem to have reversed course.
  - qingcharles 4mo ago
    They only reversed under pressure from the Safari and Firefox folks. The killing of JXL did push the ever-talented Jyrki to create jpegli, which was honestly a wonder.
    - PunchyHamster 4mo ago
      Firefox isn't even enabling it
      - Tagbert 4mo ago
        They are working on it. It is in Firefox Nightly behind a flag.
    - cyberrock 4mo ago
gcr 4mo ago
For context, Google initially refused to merge JpegXL as a strategy play to promote AVIF, which was in use by other teams (i think Photos?). Internally, chrome engineers were supportive of jxl but were overridden by leadership. I guess today’s post represents a change. I don’t have any public evidence to support my claim, sorry. Take it or leave it
- ksec 4mo ago
  I think it is quite the opposite. There were some support of JXL but leadership of Google, Android and Chrome all wanted AVIF. It was a perfect opportunity to announced AVIF with AV2, may be taking the chance to fix issues that JXL wins AV1. But that didn't happen.
JyrkiAlakuijala 4mo ago
We (Google) built JPEG XL (together with Cloudinary). The main photography mode and the JPEG compatibility mode is from Google. Chrome decided not to be an early adopter for good reasons that they have publicly documented, but that did nothing to JPEG XL. Particularly, it did not kill JPEG XL. Others, DNG, DICOM, PDF, EPUB, iOS, Safari, etc. integrated it early regardless.

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

by rowbin 4mo ago

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

rowbin 4mo ago

> Safari (2023) led among major browsers, while Firefox and Chrome currently maintain experimental support.

Gigachad 4mo ago
Maintain in a sense. Google introduced it in Chrome as an experimental flag, then removed it with no real explanation, and only just brought it back.
- halapro 4mo ago
  Which it makes perfect since this it's the same company which "deprecated" MP4 support a long while ago in an effort to push to WebM.
  - ksec 4mo ago
    Thank You I have nearly forgotten about that. At one point I was worried they might even remove AAC-LC support.
spartanatreyu 4mo ago
Yeah, but they left out that Chrome removed their own support for JPEG XL saying no one in the industry was in favour of it despite everyone seeing it was the future screaming for it and building support for it into their own products. Chrome's blink was the only major browser engine not supporting it and that prevented it from becoming a web standard and they refused to acknowledge they were wrong. Chrome only backtracked once jpeg-xl was subsumed into the PDF standard because if Chrome did not support jpeg-xl, they would by extension also not be supporting pdf.
- Gigachad 4mo ago
  jpeg xl is also now used for the latest version of the DNG raw image format, and the iphone now encodes raw images as jpeg xl in DNG. It's so clearly the future for photography that Google is holding back. Apple surprisingly has been the first with full support everywhere in their OSs and in Safari.
  - Caspy7 4mo ago
    Safari is currently lacking animation and progressive decoding - still ahead of everyone else currently. Looks like by the end of the year we can expect Chrome and Firefox support.
  - ksec 4mo ago
    I just wanted to add the decision for JXL inside DNG was well known even before it happened and Chrome still said no. Adobe and Intel along with plenty of other players in the industry screams this is so good they are all adding support. But still Google said no. And to make matter worst the publish the worst comparison document and benchmarks for AVIF against JXL.

theturtle 4mo ago

[dead]

magicalist 4mo ago

> 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.

orbital-decay 4mo ago
From what I can tell, it's written by Gemini
- deleted 4mo ago
  [deleted]
fc417fc802 4mo ago
You say that as though Google isn't notorious for killing their own successful and well received products for seemingly no reason. It's incontrovertible that Google did attempt to kill browser adoption of jxl at one point. Thankfully they seem to have reversed course.
- qingcharles 4mo ago
  They only reversed under pressure from the Safari and Firefox folks. The killing of JXL did push the ever-talented Jyrki to create jpegli, which was honestly a wonder.
  - PunchyHamster 4mo ago
    Firefox isn't even enabling it
    - Tagbert 4mo ago
      They are working on it. It is in Firefox Nightly behind a flag.
  - cyberrock 4mo ago

gcr 4mo ago

For context, Google initially refused to merge JpegXL as a strategy play to promote AVIF, which was in use by other teams (i think Photos?). Internally, chrome engineers were supportive of jxl but were overridden by leadership. I guess today’s post represents a change. I don’t have any public evidence to support my claim, sorry. Take it or leave it

ksec 4mo ago
I think it is quite the opposite. There were some support of JXL but leadership of Google, Android and Chrome all wanted AVIF. It was a perfect opportunity to announced AVIF with AV2, may be taking the chance to fix issues that JXL wins AV1. But that didn't happen.

JyrkiAlakuijala 4mo ago

We (Google) built JPEG XL (together with Cloudinary). The main photography mode and the JPEG compatibility mode is from Google. Chrome decided not to be an early adopter for good reasons that they have publicly documented, but that did nothing to JPEG XL. Particularly, it did not kill JPEG XL. Others, DNG, DICOM, PDF, EPUB, iOS, Safari, etc. integrated it early regardless.