It's a terribly inefficient format, but I think a lack of free and open video formats (and editing software) is partly to blame for its meteoric rise.
Also: video is harder to share and is typically recompressed on every upload, reducing quality.
A while ago, I tried to be a good nerd and convert some GIFs to HTML5 video, and I crashed and burned pretty hard: https://ndarville.com/asides/webvideo/.
I gained a new appreciation of GIFs that day.
That said, it would be great if we got a compromise where browsers can load only the first frame of the GIF and play the reminder on click or touch to save all the loading and data—on both sides, really.
Wouldn't a better compromise be to support MP4/WebM videos in the IMG tag? Videos embedded this way could play without audio by default (just like GIFs).
Yeah, gifs being lossless is incredibly important for remixing. This is why we must get APNG going to really improve on GIF, instead of lossy video bullshit.
GIF isn't a free and open video format either. The LZW algorithm used to compress them was patented in the 80s and didn't expire in most jurisdictions until 2003-2004.
If we want to see more efficient unencumbered video coding methods used online, the answer is most likely is going to have to come from patent reform (making patent lifetimes shorter).
The situation with H.264 isn't ideal if you're looking for purity, but licensed decoders are pretty readily available (most phones have at least one hardware decoder for it; Google/Microsoft/Apple pay to license the patents for Chrome/Windows (IE)/OS X (Safari); Cisco pays the license the patents for its binaries too).
This is such a terrible standard. Using FFprobe, one should be able to determine a video's fitness for universal playback on HTML5 streaming technologies. Automating this process is easy. I've built several high-volume media processing automation platforms for video, and never has this been a challenge for me. Could you (or others) shed some light on why devs don't do this?
I don't believe any new animated gifs should be made, except for animations such as pixel art. They are inferior in every way to html video. The success of webm on sites like 4chan are evidence that gifs offer no advantage in terms of portability, ease of sharing, or features.
HTML5 video doesn't have those constraints, and there isn't a separate type of "thing" which is an unobtrusive video. This isn't about the codec, but guaranteeing a way of presentation. Maybe if videos could be loaded into <IMG> tags with those constraints?
GIF also behaves a lot better than video when you have lots of them on a page.
"but you could disable video so you don't have issues regarding videos or some similar strawman"
Well, that would be a bit extreme, and if we want to take that angle, sure, but then I should be allowed to take the angle of "if it can be disabled by default, then instead it could be muted and paused by default"
Seriously, the whole entire point of the page is that, yes, GIF is technologically inferior and therefore wanted by no one, and therefore, allows incredible freedom of expression!
That's information we can use to make better startups!
Instead of trying to own everything and start from scratch with the most efficient artifacts like file formats, try to leverage from "inferior" techniques in order to allow the user-generated content to flourish!!!! I'm glad someone posted this!
I suppose I'm being quite negative, but I don't see the logic in that statement. In what way does it allow more freedom? The biggest advantage I think gif has at the moment is familiarity.
Really, sites just need to have a way to differentiate these types of video uploads and treat them with looping-animation UX, rather than video UX.
An easy solution would be to come up with an alternate extension for saving these videos, that other sites can recognize. This would be similar to, for example, the way iTunes knows to treat an MP4 container as an audiobook if it's an .m4b, or as a ringtone if it's an .m4r.
Another solution (and better, in my opinion) would be an extra wrapper/container document format around a video file, prepending at least a new extra magic number to allow mime-type differentiation via libmagic. I'm honestly surprised that "gifv" isn't already such a container-wrapper document format. Note that such a format doesn't need to be recognizable as a video on your computer (although support probably would be added soon enough); it just needs to be able to be reuploaded to other websites. (You could also add an extra chunk to e.g. an MKV container that, when present, would change its detected mime type—but this would restrict gifvs to only ever being MKVs. Might not be a bad thing to standardize on a video container format.)
Of course, the solution that requires no community buy-in is to just come up with a way to heuristically detect "silent short video file" on upload, and treat anything that fits those criteria as an animation rather than a video.
>They do not belong to anyone.
This may be true now, but for the majority of its lifetime GIF did not belong to everyone, due to Unisys's patent on LZW.
