Live data from Hacker News

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

opensource.googleblog.com

21–30 of 93 posts

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

#21

Huge fan of JXL, but this article feels pretty AI sloppy. Not much said here, coming from the google blog I was hoping for some news about how they are pushing the format forward by introducing decoders in to Android and enabling on Chrome. Android is the only mainstream OS that does not support JPEG XL right now.

Not to mention those IMAGES. Slop diagrams hurt

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

#24

Earlier quoted context omitted.

Yeah, but they left out that Chrome removed their own support for JPEG XL saying no one in the industry was in favour of it despite everyone seeing it was the future screaming for it and building support for it into their own products. Chrome's blink was the only major browser engine not supporting it and that prevented it from becoming a web standard and they refused to acknowledge they were wrong. Chrome only backt…

jpeg xl is also now used for the latest version of the DNG raw image format, and the iphone now encodes raw images as jpeg xl in DNG. It's so clearly the future for photography that Google is holding back. Apple surprisingly has been the first with full support everywhere in their OSs and in Safari.

Safari is currently lacking animation and progressive decoding - still ahead of everyone else currently.

Looks like by the end of the year we can expect Chrome and Firefox support.

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

#25

I'm behind -- did Chrome un-remove JXL support? Google is suddenly behind it again? Why/how did they change their minds?

They added it back as an experimental flag again. Likely the new rust based decoder and adoption in to other platforms and standards changed their decision.

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

#26

I'm behind -- did Chrome un-remove JXL support? Google is suddenly behind it again? Why/how did they change their minds?

Yes. They're adding it back to Chrome.

This last January at FOSDEM there was a panel with representatives from different browser companies. During the panel Kadir Topal, a web platform product manager at Google, indicated that because of the interest they saw in JPEG XL through the Interop Project that they changed their course on supporting it.

https://github.com/web-platform-tests/interop

The video of the panel can be found at https://fosdem.org/2026/schedule/event/7E7387-browser_in_202... . He starts speaking on the issue at about 13:00

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

#28
post #27

Mostly off topic, but why is the spec for JPEG and JPEG XL paywalled? I wouldn't call them open standards if they're not available free-of-charge to the public.

It's an open standard because the concepts and reference implementation are free and open source even if the PDF is paywalled. Realistically you could just pirate the PDF and write a jpeg xl encoder/decoder and your code wouldn't be infringing on any patents.

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

#29
post #27

Mostly off topic, but why is the spec for JPEG and JPEG XL paywalled? I wouldn't call them open standards if they're not available free-of-charge to the public.

It's an open standard because the concepts and reference implementation are free and open source even if the PDF is paywalled. Realistically you could just pirate the PDF and write a jpeg xl encoder/decoder and your code wouldn't be infringing on any patents.

Seems "closed but royalty free" would be a more accurate description then.

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

#30

> In this Gemini-reconstructed scene, ... I'm generally pretty pro-AI, but I find this icky. Of course, I wouldn't have noticed except the whiteboard drawing seemed not quite right, so I'll probably be fooled in the future.

Yep, I was totally nerd-sniped by the image. I've never seen an engineer draw a whiteboard diagram anywhere near that detailed and tidy. No acronyms, consistent title case, descenders on a baseline - everything about it is wrong. It's so counter to reality, I seriously wondered if it was a joke.

The Nano Banana team should be pissed Google PR is distributing such a terrible photo. The poses are stilted, expressions frozen, even the eye-lines are off. Why couldn't they just use a Google Pixel phone to snap a photo of real Google engineers in a real Google office and upload it to Google Photos? Not Google enough?

Post reply on HN