The saving bit is the only part which doesn't work right with videos AFAIK. Sound-less (/muted) videos can autoplay and loop, and there's no controls unless you ask for them (via the `controls` attribute) or bring your own.
The examples in the article (the scenes are videos) autoplay, loop and don't have control in either Firefox or Safari.
There are related problems like embedding. If you upload a video to Slack, say, you can’t control whether it autoplays or loops. If you upload a GIF it just works.
Your opinions are just that, and usually overridable by the client. The client could even strip your media entirely.
And gifs are pausable (used to be ESC though apparently you now need extensions).
> This way the format has no choice but to behave as expected across everything.
I've got bad news for you: once it reaches the client you're not in control anymore, you can only suggest behaviour.
IMG would autoplay, would not have sound, would loop, and would not have controls.
VIDEO would be the opposite. For something like a plain JPG or PNG file, it just shows the one frame. Animated GIF files would of course benefit from the controls.
The same should go for unification of the VIDEO and AUDIO tags. Play an audio file as video, and you get a black screen with sound. Play a video file as audio, and you just hear the sound.
Why do you hate my phone battery so much?
Your average smartphone can play 1080p video without breaking a sweat, not so with 1080p gifs. Hell, a laptop will have permanent high-CPU usage on 1080p gifs, as a video it's background noise (https://www.reddit.com/r/osx/comments/43rrf0/pixel_art_gif_a...)
That's downright hostile to the end user…
If browsers made it such that I couldn't not stop .gif animations (or playing video, or...), I would trash that browser.
Bluntly, you do not get to control my computer.
Human sight has evolved to be attracted to movement.