Gfycat - Jiffier gifs through HTML5 video conversion

Post by almosnow » Sat, Dec 28, 2013, 6:03 PM UTC

Post by puppetmaster3 » Sat, Dec 28, 2013, 6:15 PM UTC

Post by w1ntermute » Sat, Dec 28, 2013, 6:30 PM UTC

kristofferR wrote: post #13

dopamean wrote: post #11

Earlier quoted context omitted.

Is OTOH really an acronym people are using now?

AFAIK, yeah.

Post by teleclimber » Sat, Dec 28, 2013, 6:36 PM UTC

bri3d wrote: post #28

fosap wrote: post #25

Earlier quoted context omitted.

No, every mobile can process a 80ties picture format in tiny resolutions. 90ies computers could do that without a problem without any allocation an needed only a fraction of their cpu. Now we have quadcore cpus clocked at >1 GHz in our mobiles. It's just the saved bandwidth. And, btw, hardware allocation is a way overrated. There is a HEVC software implementation for the iphone. Just compare the complexity of HEVC to…

The problem isn't the peak capability of the hardware: it's the strategy used to handle the content. In most web browsers animated GIFs are treated as images, which depending on the browser causes a whole host of potential side-effects (kept around or animating when offscreen, all frames kept in memory, etc.) Video is video and is in general more properly streamed, evicted from memory, and halted when offscreen.

Post by rett12 » Sat, Dec 28, 2013, 6:58 PM UTC

barrkel wrote: post #6

GIF is a terrible format for video, but OTOH it's fairly lightweight for the browser for simple animation. Historically, playing video in the browser has required loading plugins, increasing the attack surface of the browser quite a bit, as well as inflating memory usage, increasing fragility, etc. HTML5 video is also blocked by my flash blocker. Up until the latest version of Firefox, animated gifs were blocked by m…