> My point was nowhere nearly as interesting as if a specially crafted gif somehow triggered a memory leak in a driver when rendered.

There's absolutely no mention of "specially crafted" GIF or "when rendered" in the title. You're projecting your expectations which have nothing to do with the story and are not even hinted at by the title, and choose to be offended that they get betrayed. There are many things I'd like to retort here, but the most important is that it's against the HN guidelines, so it would be good if you stopped.

What's a GIF? An image format.

What's done with image formats? They are viewed.

The default thought if someone says they opened a gif isn't "they splayed open the hundreds of frames for individual manipulation" anymore than someone saying "Car moved from point A to point B" would mean "Car disassembled and moved piece by piece from point A to point B"

And I don't recall the rule asking you to backseat mod :) Nothing against the rules in explaining simple nuances of written word

> Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.

> Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.

Good thing I'm just explaining simple nuance then!

And please make an announcement about your promotion to mod :)

I wish I was a mod! I could easily check just how many downvotes this whole thread gave you. Now the only thing I can do is to soothe my eyes by looking at all the wonderful shades of grey here.

Where do you see anything about individually opening 730 frames, and why would it be unsurprising for that tiny load to cause a bug? Have you heard of video editors? The same machine can edit four 4K@60fps streams.

Oh my god. I get it. You’re reading the headline as “this GIF uses xx memory”. That’s not what is says. It’s “GIF uses X memory on x86, X*10 memory on M1”. You’re picking a fight based on your own misreading.