jxl-rs

That’s not at all how it went. Years ago, both Chrome and Firefox had experimental support. In October 2022, Chrome suddenly announced their decision to drop it (citing dubious reasons like lack of interest or improvements over existing formats). [1] It was only later, in January 2023, that Mozilla announced their formal position of not really caring about the format. [2] In October 2023, one of the JPEG XL devs said that the responsible team at Google was ready to write a decoder in Rust if that was the only reason holding adoption back, even offering to work on browser integration. [3] One month later, another dev confirmed that a different pre-existing decoder written in Rust was already standard-conformant. [4] It wasn’t until September 2024, nearly a whole year later, that Mozilla changed their official position from not caring to wa

> Removed because having yet another giant C codec was a huge risk Removed because trillion dollar advertising company don't bother, which also happens to be the browser vendor monopoly. How many man-hour effort does it take to create jxl-rs ? https://github.com/libjxl/jxl-rs/graphs/contributors

Not sure why you’re being downvoted… there is an issue open on the JPEG-XL Rust repo for this very feature. https://github.com/libjxl/jxl-rs/issues/513

https://github.com/libjxl/jxl-rs jxl-rs is the underlying implementation. It's relatively new but Rust certainly calms security fears. This library wasn't really an option last time this came around in chromium.

jxl-rs https://github.com/libjxl/jxl-rs was referenced as a possibility; what library is Safari using for jpegxl?

Finally. I was wondering how long it would take them. For scanned documents with OCR, it makes a lot of sense. At same quality you get significantly smaller files, especially when looking at above 300dpi. JPEG keep getting extensions like ultra HDR (which really is a hack more than anything else), XYB JPEG (significantly higher compression efficiency than classic jpeg), but all of these habe very limited support tbh, hence introducing jpeg xl seems more logical. The only downside of jpeg xl to me is that it doesn’t support gain maps (yet?[1]). Without gain map, you have limited control over how the SDR image looks like, which can be very problematic in environments where you don’t know what the hardware presenting the image will be in the end. But the list of upsides is so long: * higher bit depth * native HDR (no hack) * better compressi

There's way more than one rust implementation around - https://github.com/libjxl/jxl-rs - https://github.com/tirr-c/jxl-oxide - https://github.com/etemesi254/zune-image Etc. You can wait for 20 or so years "just to be sure" or start doing something. Mozilla sticks to the option A here by not doing anything

You can review it here: https://github.com/libjxl/jxl-rs Seems to be under very active development.

Then why did they develop libjxl, and why are they working on jxl-rs? https://github.com/libjxl/libjxl/blob/main/AUTHORS https://github.com/libjxl/jxl-rs/blob/main/AUTHORS Maybe their stated reason for not enabling support in Chrome is the actual reason.

> rust rewrite of libjxl See: * https://github.com/libjxl/jxl-rs

JXL is still alive and well, it's just taking time to reach the prime time. - Mac OS, iOS, and Safari support JPEG-XL - Windows has first party JPEG-XL support as of this year (admittedly it's opt in rather than default) - Essentially every major image processing app, editor, or drawing app supports JPEG-XL - Firefox has preliminary support for JPEG-XL gated behind a feature flag and the nightly release. - The JPEG-XL team is writing a direct port of the reference libjxl library into rust[1]. There already exists a third party rust port by some of the mainline contributors and it has ironed out a lot of the issues with the porting process prior to this mainline port. This first party rust port is intended to be gradually brought up to a hardened, production ready state. - Mozilla has stated they have no objections to fully adopting JPEG-X

It's not yet the end, a rust decoder is on the way: https://github.com/mozilla/standards-positions/pull/1064#iss... One day, people will wonder why it took so long, and I'll smile =) That's the decoder: https://github.com/libjxl/jxl-rs (why they couldn't use jxl-oxide, I don't know) Also good to know, the ff nightly feature for jpeg xl currently does NOT use the aforementioned decoder, it uses something else, hence it's worthless for testing at the moment...

> JPEG-XL seemed like the next logical step until Google took their toys and killed it despite already having the support in Chrome, which pretty much makes it dead in the water (don't you just love monopolies making decisions for you?) It's worth noting that Firefox is willing to adopt JPEG-XL[1] as soon as the rust implementation[2] is mature And that rust impl is a direct port from the reference C++ implementation[3]. Mac OS and Safari already support JPEG-XL [4]. And recently Windows picked up JPEG-XL support. The only blockers at this point are Firefox, Chromium, and Android. If/when Firefox adopts JPEG-XL, we'll probably see google follow suit if only out of pressure from downstream Chromium platforms wanting to adopt it to maintain parity. So really if you want to see JPEG-XL get adopted, go throw some engineering hours at the rust

Two rust implementation projects : https://github.com/tirr-c/jxl-oxide https://github.com/libjxl/jxl-rs