News for hackers. Stuff that matters.
Re:Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likel... by paulryanrogers on Friday May 21, 2021 @08:25AM (#27233129)
Why not cap animated gifs at a maximum duration or file size? GIFs original use cases are already served by formats better suited to the modern era.

Their continued popularity seems due mostly to their historical auto play behavior. One that apps are so reluctant to disrupt we're filling landfills with electronic waste to keep up with ever larger and longer meme animations.

Re:Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likel... by slver on Friday May 21, 2021 @08:39AM (#27233254)
It's too late to (re)define GIF.

Actually software which edits animated GIFs doesn't have to crash per se, it's all about how smartly it's implemented, and because GIF editing isn't exactly a sprawling industry, most apps tend to be, well, not that smart, and so edge cases can get them.

Re:Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likel... by paulryanrogers on Friday May 21, 2021 @08:47AM (#27233334)
Formats don't have to be fully implemented to their original spec for all time. If it's not serving us well today then we can change how our software uses it.
Re:Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likel... by Wowfunhappy on Friday May 21, 2021 @09:10AM (#27233545)
They kind of do, though, or you lose compatibility.

There are a lot of corners of the internet which just haven’t been touched in a decade. Are you going to break all of them? For what purpose?

Re:Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likel... by paulryanrogers on Friday May 21, 2021 @09:37AM (#27233815)
Is it really much of a loss that very large or long GIF animations required click-to-play?
Re:Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likel... by oauea on Friday May 21, 2021 @04:23PM (#27239446)
Yes, it would be immense. Many gifs have been used for user interface elements and such a change would break that completely.
Re:Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likel... by paulryanrogers on Friday May 21, 2021 @09:20PM (#27242250)
I'm not suggesting some modest, >1KB spinners should be gated like this.

Rather that renderers / apps would put a pause on downloading and processing very large (say 1MB+) or very long animations (100+ frames).

Re:Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likel... by oauea on Saturday May 22, 2021 @01:32AM (#27243797)
I think you are underestimating gif sizes if you think a 1MB gif is large.
Re:Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likel... by burnished on Sunday May 23, 2021 @12:35AM (#27252489)
but would your example, crucial, gif ui elements be that large? that seems odd
Re:Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likel... by beckingz on Friday May 21, 2021 @09:07AM (#27233516)
Wouldn't it be better to make a new specification that provides backwards compatibility?
Re:Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likel... by paulryanrogers on Friday May 21, 2021 @09:39AM (#27233844)
If the goal is to stop obscene memory and bandwidth bloat then changing the default to a click-to-play/load would be better. My thinking is too change the incentives so producers aren't exploiting an old format to force autoplay at the expense of wasted resources and user control.
Re:Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likel... by niutech on Monday May 24, 2021 @10:15AM (#27264607)
You can use <video autoplay loop muted playsinline> for an auto-playing cross-browser animated GIF replacement.