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.
My guess is that the original whiteboard probably contained a mix of messy drawings and confidential stuff, and whoever assembled this article asked gemini to make the whiteboard look nicer. The first thing I noticed was that the drawings and labels look too neat compared to what I usually see on whiteboards, and the second thing I saw was the gemini watermark in the corner.
> That's rich coming from the company that tried to kill it
This post is written by three of the authors of the JPEG XL spec, implementors of the reference and rust implementations of libjxl, and...longtime google employees.
> 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.
Came here to say the same thing. Why add this fake image?
My guess is that the original whiteboard probably contained a mix of messy drawings and confidential stuff, and whoever assembled this article asked gemini to make the whiteboard look nicer. The first thing I noticed was that the drawings and labels look too neat compared to what I usually see on whiteboards, and the second thing I saw was the gemini watermark in the corner.
Weird 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
That's rich coming from the company that tried to kill it. The audacity...
> That's rich coming from the company that tried to kill it
This post is written by three of the authors of the JPEG XL spec, implementors of the reference and rust implementations of libjxl, and...longtime google employees.
From what I can tell, it's written by Gemini
Yup just a little bit too much em dashes.
> Safari (2023) led among major browsers, while Firefox and Chrome currently maintain experimental support.
Out of experimental when?
AI slop article