h264ify

h-performance software decoders. VP9 implementations have been increasingly optimized over the years but it's really challenging to beat hardware performance even before you consider the power budget. As a simple example, I opened https://www.youtube.com/watch?v=wbSwFU6tY1c on a 2.13 GHz Intel Core 2 Duo (2010 MacBook Air). That's playing a 1280x720 stream. In all browsers, even with ads blocked by /etc/hosts I had to wait ~20 seconds for the 80+% CPU from the YouTube JavaScript to settle down before starting playback. In Safari, that video takes between 3 and 8% CPU usage with no dropped frames. In Chrome, that's 80-120% CPU usage and about a 5% dropped frame rate. Firefox is interesting: it ran at about 15-20% CPU usage, which is worse than Safari but still much better than Chrome. I thought that was odd but stats for nerds showed why: Firefox was using H.264. After using media.mediasource.webm.enabled to forcibly enable webm, it started using VP9 and that meant ~40% CPU with bursts up to about 80%. While that's clearly much better than the Chrome experience it's still a full order of magnitude more CPU than Safari's hardware path. Remember, I'm not saying that VP9 is horrible but rather than hardware support is a really big deal and optimized video playback in general has non-trivial costs. Apple made a big investment in HEVC and it doesn't surprise me that they're investing in the next generation rather than spending time on the current generation since the fixed costs for tuning, testing, security, etc. are the same whether 100% or 5% of your customers use it.