GIF should be killed. Animated PNG is where it's at.
Animated PNGs should be killed. Just embed a video with an alpha channel. It compresses way better.
Wrong use-case. Animated GIFs and animated PNGs were never intended for video. The analogy to still image formats is video:JPEG = web-animation:PNG. You don't save screenshots as JPGs and you don't save photos as PNGs. Same with video and web-animation, two different use-cases require two different formats.
except that's a false dichotomy
one format can support both lossy and lossless images and use better compression between frames to achieve 10x better results for animations than animated pngs without visible loss of quality
Which format can support both lossy and lossless images?
I spent 2 seconds in GIMP to make the following GIF: http://i.cubeupload.com/kbrcfQ.gif Please show me the video format that can replace it.
webp supports animations, lossless and lossy images, etc.
I already linked to a video with an alpha channel that can match your gif
When you can only post/upload content that end up inside img tag, it's not a false dichotomy.
Re:Introducing the ‘mozjpeg’ Project
by TheZenPsycho on Thursday March 06, 2014 @04:29PM
(#7356745)
meanwhile, back in the real world, gifs and apngs are staying exactly where they are.
What would be great if there was some way for an animated gif's frame delays to opt-in to being interpreted correctly by browser- That is, a 0-delay really would display with no delay, and so optimisation strategies involving the splitting of image data across multiple frames could be done- and when read in by a browser, all frames would be overlaid instantly, module loading time.
What other things can be done to further optimise animated gif encoding?