5 ms·

Gif was killed a long time ago by webm

• asdff 7y ago
  Last I checked my iPhone can't do webm or webp
  • clouddrover 7y ago
    You can support a variety of formats in Safari using WebAssembly builds of the decoders. WebAssembly for audio and image formats is more than fast enough. It's even fast enough for VP9 video. WebP demo: https://webmproject.github.io/libwebp-demo/webp_wasm/index.html https://webmproject.github.io/libwebp-demo/webp_wasm/index.h... Theora\VP8\VP9\Opus\Vorbis demo: https://brionv.com/misc/ogv.js/demo/ https://brionv.com/misc/ogv.js/demo/ ogv.js on GitHub: https://github.com/brion/ogv.js https://github.com/brion/ogv.js
    • Spivak 7y ago
      Is it really worth it to ship a decoder to every user of your site rather than encode it once on your server? Don't get me wrong, it's a super cool demo but anyone who does this is prod is a little nuts. The exception being a service that's write once read maybe like CCTV cameras.
      • clouddrover 7y ago
        You still encode the file once on the server. The decoder just happens to be implemented in WebAssembly. Wikipedia uses ogv.js. If you've ever played audio or video on Wikipedia in Safari then you've used ogv.js. Some Bach on Wikipedia in Safari: https://en.wikipedia.org/wiki/File:Chromatic_Fantasia_(Bach_BWV_903).ogg https://en.wikipedia.org/wiki/File:Chromatic_Fantasia_(Bach_...
      • d0ugie 7y ago
        It's all gravy, the javascript WebP decoders, until you convert your 20K high res photo site to WebP, then not realizing for a week, scratching your head about the bounce rate spiking, that you're crashing browsers left and right...
• King-Aaron 7y ago
  webm killed nothing.