3 ms·

> JXL was dead. Apple is who brought it back to life No, it was actually the PDF Association. They added JXL to the PDF standard. If google wanted to maintai

> JXL was dead. Apple is who brought it back to life No, it was actually the PDF Association. They added JXL to the PDF standard. If google wanted to maintain support for displaying PDFs, they would need to add support for JXL.

NewJazz 1mo ago
* wanted to maintain support for displaying jxl images that are embedded in PDFs
llm_nerd 1mo ago
The PDF consortium added JXL to the PDF spec two years after Apple deployed support to billions of devices. To anyone ackchyually paying attention to the JXL spec, lamenting that this superior format wallowed in obscurity (largely, it should be noted, because Google dumped it, and so many others just follow the leader of Google), Apple actually completely changed the path of the format's adoption.
- cbolton 1mo ago
  To summarize the timeline: 2015-2021: Google and Cloudinary develop the technical foundations, work on standardization with the JPEG group and write the reference implementation 2021: Chrome and Firefox introduce experimental support 2022: The Chrome team decides to remove the experimental support, citing lack of interest in the ecosystem 2023: Apple surprises by shipping support in all their products 2024: Firefox says they don't want the attack surface of 100K lines of multithreaded C++ but they will ship support if Google implements a Rust version September 2025: Google delivers jxl-rs v0.1.0 (a Rust implementation) October 2025: The PDF Association announces they want to include the format in PDF, citing the need for HDR support in particular November 2025: The Chrome team reverses its position, citing Safari support, Firefox's new stance, Interop proposals and the PDF announcement. So while Google played the largest part by far in making JPEG-XL a thing, Apple probably played an outsize role in getting it adopted so fast. But its long-term fate? Who knows... The PDF Association might well have adopted JPEG-XL without Apple: they cited HDR support, wide-gamut, ultra-high resolution and channel number, not "works on iOS". And having it as the format for HDR in PDF would have forced Chrome's hand no matter what Apple did. (Small heads up: the "anyone with a clue agrees with me" framing is more grating than useful.)
alwillis 1mo ago
>> JXL was dead. Apple is who brought it back to life > No, it was actually the PDF Association. The PDF Association didn't adopt JPEG-XL until September 2025. By then, Apple had been shipping JPEG-XL in Safari for two years [1]. So there's that. [1]: https://webkit.org/blog/14205/news-from-wwdc23-webkit-features-in-safari-17-beta/#images https://webkit.org/blog/14205/news-from-wwdc23-webkit-featur...

NewJazz 1mo ago

* wanted to maintain support for displaying jxl images that are embedded in PDFs

llm_nerd 1mo ago

The PDF consortium added JXL to the PDF spec two years after Apple deployed support to billions of devices. To anyone ackchyually paying attention to the JXL spec, lamenting that this superior format wallowed in obscurity (largely, it should be noted, because Google dumped it, and so many others just follow the leader of Google), Apple actually completely changed the path of the format's adoption.

cbolton 1mo ago
To summarize the timeline: 2015-2021: Google and Cloudinary develop the technical foundations, work on standardization with the JPEG group and write the reference implementation 2021: Chrome and Firefox introduce experimental support 2022: The Chrome team decides to remove the experimental support, citing lack of interest in the ecosystem 2023: Apple surprises by shipping support in all their products 2024: Firefox says they don't want the attack surface of 100K lines of multithreaded C++ but they will ship support if Google implements a Rust version September 2025: Google delivers jxl-rs v0.1.0 (a Rust implementation) October 2025: The PDF Association announces they want to include the format in PDF, citing the need for HDR support in particular November 2025: The Chrome team reverses its position, citing Safari support, Firefox's new stance, Interop proposals and the PDF announcement. So while Google played the largest part by far in making JPEG-XL a thing, Apple probably played an outsize role in getting it adopted so fast. But its long-term fate? Who knows... The PDF Association might well have adopted JPEG-XL without Apple: they cited HDR support, wide-gamut, ultra-high resolution and channel number, not "works on iOS". And having it as the format for HDR in PDF would have forced Chrome's hand no matter what Apple did. (Small heads up: the "anyone with a clue agrees with me" framing is more grating than useful.)

alwillis 1mo ago

>> JXL was dead. Apple is who brought it back to life > No, it was actually the PDF Association. The PDF Association didn't adopt JPEG-XL until September 2025. By then, Apple had been shipping JPEG-XL in Safari for two years [1]. So there's that. [1]: https://webkit.org/blog/14205/news-from-wwdc23-webkit-features-in-safari-17-beta/#images https://webkit.org/blog/14205/news-from-wwdc23-webkit-featur...