> 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.
Based on what I've heard, Google is monitoring per-org usage and strongly / incessantly encouraging teams to experiment with the technology, so a lot of tokens get spent on pointless stuff like that. The preceding diagram, which is needlessly busy and blurry, appears to be AI-generated too.
Journey to JPEG XL: open-source experiments shaped the future of image coding
61–70 of 93 posts
Re: Journey to JPEG XL: open-source experiments shaped the future of image coding
#62> 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.
Came here to say the same thing. Why add this fake image?
Re: Journey to JPEG XL: open-source experiments shaped the future of image coding
#63Weird they don't name Jon Sneyers - a person pivotal in creation of JPEG XL Here's a blog post by him: https://cloudinary.com/blog/2026-the-year-of-jpeg-xl
Re: Journey to JPEG XL: open-source experiments shaped the future of image coding
#64That's rich coming from the company that tried to kill it. The audacity...
Chrome decided not to be an early adopter for good reasons that they have publicly documented, but that did nothing to JPEG XL. Particularly, it did not kill JPEG XL. Others, DNG, DICOM, PDF, EPUB, iOS, Safari, etc. integrated it early regardless.
Re: Journey to JPEG XL: open-source experiments shaped the future of image coding
#65Earlier quoted context omitted.
You say that as though Google isn't notorious for killing their own successful and well received products for seemingly no reason. It's incontrovertible that Google did attempt to kill browser adoption of jxl at one point. Thankfully they seem to have reversed course.
They only reversed under pressure from the Safari and Firefox folks. The killing of JXL did push the ever-talented Jyrki to create jpegli, which was honestly a wonder.
Jpegli is still a hidden gem. People don't yet understand how great it is.
Re: Journey to JPEG XL: open-source experiments shaped the future of image coding
#66AI slop article
Re: Journey to JPEG XL: open-source experiments shaped the future of image coding
#67I personally think something like the qok format is a better way to go. Make something that performs well and is dirt simple to implement.
Also, it is not a competition for the shortest specification. If it was, still good. Jpeg xl spec is about half the size of the original jpeg spec.
Re: Journey to JPEG XL: open-source experiments shaped the future of image coding
#68Mostly 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 a standard ISO Standard thing which could perhaps be justified when standards where printed on paper. The JPEG XL team released a draft to try to work around this but couldn't avoid it for the official standard release.
Re: Journey to JPEG XL: open-source experiments shaped the future of image coding
#69The sloppa in this article is... offending. The obvious AI headings, pointless genned image of people (I'm starting to think islam had a point with discouraging depictions of human figures), and especially the blurry, artifacted, distractingly skeuomorphic diagram, with random wire traces going everywhere... this is a technical blog, not an investor sales pitch! Every time I see one of these, I have to double-check f…
I spent 10+ years in building JPEG XL and I'm proud of the result. It wasn't always easy times. It is not so bad people can see what I look like and take a peek what the process was to get there. This article is not about the entropy codes and predictors, memory bandwidth and decision trees, but about the long horizon planning in corporate-driven OSS efforts and being connected to both community and cross-industry.
Re: Journey to JPEG XL: open-source experiments shaped the future of image coding
#70That's rich coming from the company that tried to kill it. The audacity...
For context, Google initially refused to merge JpegXL as a strategy play to promote AVIF, which was in use by other teams (i think Photos?). Internally, chrome engineers were supportive of jxl but were overridden by leadership. I guess today’s post represents a change. I don’t have any public evidence to support my claim, sorry. Take it or leave it
It was a perfect opportunity to announced AVIF with AV2, may be taking the chance to fix issues that JXL wins AV1. But that didn't happen.