this post was submitted on 04 Feb 2024
211 points (87.8% liked)

Technology

59438 readers
3544 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
L3s@fry.gs
L4s@fry.gs
L4s@lemmy.world
enu@lemmy.world
211
Browser maker love-in snubs Google-shunned JPEG XL (www.theregister.com)
submitted 9 months ago by AnActOfCreation@programming.dev to c/technology@lemmy.world
54 comments fedilink hide all child comments
 
  • Browser makers Apple, Google, Microsoft, and Mozilla have announced Interop 2024, a project to promote web browser interoperability.
  • JPEG XL, a potential replacement for JPEG and PNG image formats, was not included in Interop 2024.
  • The rejection of JPEG XL has been blamed on Google, with the Google Chrome team deciding not to support the image compression technology.

Archive link: https://archive.ph/nulY6

you are viewing a single comment's thread
view the rest of the comments
[–] redcalcium@lemmy.institute 46 points 9 months ago (2 children)

Thanks to wasm, you don't have to bow to Google's whim and can choose to include jpeg xl support on your websites if you want: https://github.com/niutech/jxl.js

[–] 2xsaiko@discuss.tchncs.de 5 points 9 months ago (1 children)

Do you know if it uses the native decoder if available (so, in Safari I guess)? Doesn't say in the readme.

[–] redcalcium@lemmy.institute 12 points 9 months ago* (last edited 9 months ago) (1 children)

I believe so. This line in the source code means it'll only attempt the decoding if an img element for a .jxl image url fails to load.

If you're on safari, you can verify it by going to the demo page at https://niutech.github.io/jxl.js/ and inspect the image element. If the src attributes contain blob, then it's decoded using the wasm decoder. If the src attribute contains url to a .jxl file, then it's decoded natively.

[–] 2xsaiko@discuss.tchncs.de 1 points 9 months ago

Very cool, thanks. Will keep this in mind.