Apngasm Wants To Promote Animated PNGs As An Alternative To GIFs
techcrunch.com
techcrunch.com
why? Is the word orgasm so scary to you?
And decade of this situation has conditioned us to think that only shitty video formats (like GIF, APNG, WebP with animation) can be allowed to have first-class support in browsers, and any video format that is technically competent must be kept isolated in special tags, must not work well with rest of the browser and must cargo-cult limitations of plugins of the '90s.
But browsers can and do support H.264/WebM natively now. Technically (patents aside) we could have <img src="video.mp4-or-webm"> work just as well as GIF (and maybe even faster given 10th of bandwidth needed and possibility of HW acceleration).
Don't forget that we now have javascript, CSS animations, canvas and webgl in addition to good old gifs to deal with animated features. Do we really need apng on top of that?
Little emoticon stuff makes more sense with GIF which are very inefficient with filesize but with very very little performance overhead.
This is just 'my gut' like you have said. A proper analysis of the performance of h.264/GIF vs resolution would be nice though.
I can think of one other hypothetical problem, although it would need testing to confirm: block sizes. h.264 works with block sizes that are a multiple of 4, and AFAIK codecs often perform sub-optimally with input that cuts off mid-block. For large videos that doesn't matter much, since you don't usually focus on the edge of a video, but for a small asset, it might be a problem. Someone with more knowledge of h.264 might be able to correct me on this.
While much more efficient in the long run, a video codec loses out for short animations when you consider the above points.
There is simply no way that you are going to achieve more efficient compression with that crude technique than with the algorithms used by modern video codecs.
I also think that losslessness is probably relatively low concern with an animation.
The transparency thing is important, although that is achievable with video as well. WebM is apparently going to support it directly one of these days, but the cross-browser way is to store the alpha channel in a separate half of the frame and combine them using an off-screen canvas. (Edit: see this demo: http://jakearchibald.com/scratch/alphavid/)
I want all video on sites to never autoplay solely because of sound.
A good animated picture format could be similar in size to video, while maintaining the advantages of a gif.
HTML5 video wasn't uniformly supported across browsers (and remember Google announced Chrome would drop h.264 around that time) and I didn't get positive responses on the idea. Maybe with more tools to support HTML5 video in animated GIF use cases and educational tools showing the difference in loading times and encoding algorithms this idea could take hold.
Also the WebP engineers have developed an animated WebP format which I disagree with but could be a step toward breaking GIF's monopoly on short animations.
It's still the case, IMHO. For example, mobile devices are a lost battle, in my experience, when it comes to HTML5 video (with autoplay and without controls). So MC ends up serving the straight up GIF to them.
I hope animated WebP becomes a thing but I have my doubts. I'm not sure whether the three major browsers will support it to an extent that it's actually sensible to use animated webp.
Here's an example of an increasingly-popular idiom on the web where embedded video doesn't quite do as good a job as animated GIFs.
I'm sorry for sharing this, but it is both timely (it's about some music award event yesterday evening) and relevant:
http://www.buzzfeed.com/lyapalater/the-weirdest-and-craziest...
If anything, though, this makes a case for not creating yet another tool for this kind of expression.
Building extensions/plugins to increase quality is not only missing the point, it's directly opposed to it.