RE: https://techhub.social/@LinuxToday/116755292106088778

OMG IT’S HAPPENING JPEG XL FINALLY!!!!!

AAAAAAA

AAAA
A
AA
AAA

#JPEGXL #JXL #Firefox

Maybe someone can correct me, but wasn't #JPEGXL half deprecated because the browsers didn't want to support it just a year or two ago? This article makes it sound like #Google was pushing towards it and fully supporting it. Excited to see some love for it though.

https://opensource.googleblog.com/2026/06/journey-to-jpeg-xl-how-open-source-experiments-shaped-the-future-of-image-coding.html

Journey to JPEG XL: open-source experiments shaped the future of image coding

https://opensource.googleblog.com/2026/06/journey-to-jpeg-xl-how-open-source-experiments-shaped-the-future-of-image-coding.html

#HackerNews #JPEGXL #open-source #imagecoding #technology #experiments #futureofimages #digitalinnovation

RE: https://chaos.social/@chrysn/116634862591473927

@jonsneyers Could you help me figure out whether this JXL trick is realistic or I'm trying to catch a ghost?

I'm serving image thumbnails on file shares and later on the web; some use cases just use 64x64px, some want 2k. Pre-JXL I'd have stored binary steps and told the browser in a srcmap. Can a progressive encoder drop hints like "for 128px, you'll be reasonably done by 4015 bytes"? (And then there's the question of how to tell the browser so it can request ranges.)

#jxl #jpegxl

"so basically AVIF is the new JPEG, and JPEG XL is the new PNG."

#avif #jpegXl #jxl