←back to thread

The JPEG XL Image Coding History, Features, Coding Tools, Design Rationale

(arxiv.org)
94 points ksec | 1 comments | 13 Jul 25 05:05 UTC | HN request time: 0s | source
Show context
ekunazanu ◴[15 Jul 25 11:29 UTC] No.44570052[source]▶
JPEG XL had so much going for it. Kinda sad it was killed off just like that.
replies(7): >>44570077 #>>44570161 #>>44570521 #>>44570580 #>>44570956 #>>44572410 #>>44575108 #
MrAlex94 ◴[15 Jul 25 11:47 UTC] No.44570161[source]▶
As it currently stands there should be over a billion devices that natively support JPEG-XL, as it was introduced in all Apple OSs since September 2023[1].

On the web alone it should be close to a billion users with support for JXL due to Safari’s market share.

[1]: https://cloudinary.com/blog/jpeg-xl-how-it-started-how-its-g...

replies(1): >>44570272 #
ndriscoll ◴[15 Jul 25 12:04 UTC] No.44570272[source]▶
It's also supported in Windows, GNOME, KDE, pretty much all image editors/viewers, and pretty much every other relevant program except for chromium based browsers.
replies(1): >>44570437 #
account42 ◴[15 Jul 25 12:27 UTC] No.44570437[source]▶
Not just Chromium-based browsers, Firefox as well. Might not make much of a difference for user counts but it does mean that so far it's available on the web is limited to a single vendor.
replies(4): >>44570458 #>>44570622 #>>44570623 #>>44570649 #
kevincox ◴[15 Jul 25 12:52 UTC] No.44570623[source]▶
Firefox has it implemented (behind a preference on nightly). They just don't want to ship it if Chromium isn't going to because it would cause fragmentation in the web and something they have to maintain forever for a minority of sites (as most won't bother if Chromium based browsers don't support it).
replies(3): >>44571016 #>>44571743 #>>44573484 #
1. OneDeuxTriSeiGo ◴[15 Jul 25 13:35 UTC] No.44571016[source]▶
Tbh it's less about having to maintain it forever and more about not wanting to deal with maintaining a C++ library codebase that would widen the potential attack surface of the browser (due to memory bugs, etc). They are fine adopting it as long as it's in rust (which is being worked on, see sibling comments)