gutechh

Indeed, the solutions in search of a problem are teeming in the day and age of LLMs! I think the opposite framing is quite interesting aswell "solutions in search of a problem" -> "problem in search of a solution" as in solution are not always self evident and what might work for one might not work for someone else, striking the right balance takes time. And to me this article highlight this, they are academics that are well aware of problem at hand, but still, they can't easily formulate a solution to it.

Thank you! I wonder if we'll ever see avif/webp takeover or if it's gonna be like ipv4/ipv6.

Thanks for these! Indeed I understand your point now. I'll add a little note on the post later today.

Another interesting bit is that It wasn't so easy to get an image showing the issue a clear as we had it. My hunch is that moiré patterns might have a role in this, as most images where the the issue showed, had some kind of grid/repetition. I suppose some images might be more affected by the IDCT and other more affected by the scaling algorithm, making it more or less visible. It's a mix like you said!

Ah this is weird! My understanding is that png doesn't store the images like jpg at all, they use a palette of all the colors in the image. Then each pixel is a reference to this palette. So it's not IDCT scaling, but I imagine there are other tricks to save on space/cpu when decoding pngs.

Yes! for a bit of backstory, it was an internal icon on a prototype that we were polishing up. So I get why the person did it at the time, running after the svg would have been too much effort for something that might have been tossed in the end.

Thanks, I knew it was much more efficient, but seeing the numbers in the benchmarks make me appreciate this "trick" even more!

ahah, yeah surprising considering how Chrome is RAM hungry, 20mb isn't that much of a win. On another end when trying to reproduce the glitch, it was quite hard! basically invisible on photos and not all icons were affected. So it does work very well. It was kind of our fault to use a jpg for an icon ahah.

Ah! It took a fair bit of digging to get there. Maybe I'll look into the firefox pipeline and make another post. In the mean time if anyone know the internals and how firefox does it, I'm eager to hear about it!

I do prefer the firefox look too! I'd be curious to hear your take on what could be the root cause of this. I'm far from a image rendering expert. But I remember when inspecting the edges and curves of the images in a DCT visualizer they were all in the AC coefficients which is what led me to the conclusion of the post.

Maybe you read them already, but wikipedia has a bunch of interesting pages about sourcing and truth like: https://en.wikipedia.org/wiki/Wikipedia:Verifiability,_not_t... and https://en.wikipedia.org/wiki/Wikipedia:Reliable_sources