Linux @lemmy.ml Leaflet @lemmy.world 3 days ago

Firefox will consider a Rust implementation of JPEG-XL (with Google's help)

github.com Firefox will consider a Rust implementation of JPEG-XL by bholley · Pull Request #1064 · mozilla/standards-positions

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

Firefox @lemmy.ml Leaflet @lemmy.world 3 days ago

github.com /mozilla/standards-positions/pull/1064

27 comments

I have a nagging doubt; jpeg-xl has a very extensive feature set (text overlays, etc). meanwhile, tech/media consortia want a basic spec for AV1 + OPUS on chip and push that to all media capable devices. we can expect av1, avif and opus to be ubiquitous in a few years. So i think they will prioritise AVIF.
JXL is based.
- I took my existing JPEG file, compressed it using JXL, 15% smaller.
  
  Then I decompressed it again into JPEG. The file was bit-for-bit identical to the original file (same hash). Blew my mind!
  
  Directly using JXL is even better of course.
  
  So it's called xlarge... And it makes files smaller.
  
  Why.
Google's involvement should always raise concerns but I guess it's good Mozilla is trying to improve stuff.
- this is from the google research team, they contribute a LOT to many foss projects. Google is not a monolith, each team is made of often very different folk, who have very different goals
  
  As long as their goals suite the company, sure. The endgame of Google is very clear and it doesn't include a free and open web.
  
  Well Google can still lock Mozilla out of the features and cooperation if they do something Google doesn't like. It's just one example. Nobody should ever trust Google.
  
  Its 2024 and this guy is telling us that google is not so bad.
Please let this happen!
Think the headline kind of buries the lead. Firefox is basically holding google by the balls and saying "Make a better decoder if you want this shit to become standard" which imo is great. Force them to do what they should have done already.
- if you want this shit to become standard
  
  Since when Google is interested in promoting jxl and not webp?
- This is not right on multiple levels. Google, or at least the chromium team were not interested in implementing jxl at all
  
  maybe i misunderstood what they were saying on github then cuz to me it sounded like they were using their leverage as firefox to get a decoder made that was more secure.

You've viewed 27 comments.