4 ms·
a) Why not do the same to embedded videos? b) The only affected browser is Safari. Edge and Firefox remain unaffected. c) How many people actually watch 4K vi
by guitarbill 10y ago
a) Why not do the same to embedded videos?
b) The only affected browser is Safari. Edge and Firefox remain unaffected.
c) How many people actually watch 4K videos, and how many videos are 4K?
So let's not go overboard on the conspiracy theories. For all we know, it could be a bug.
- milankragujevic 10y agoIt's most likely not a bug, as YouTube and Google are known for forcing VP8/9/10/A1 down people's throats, because it's theirs and they want to "show it to Apple". For video sites, H.264 is the only option if they want to support Apple devices, and it's hardware decoding is widespread enough that it doesn't cause any issues. The only issue is it's patented and it's bad at encoding compared to VP9/H.265. But we can just switch to H.265 anyways, and given that Google deprecates their codecs every 2 years, I don't think that they will ever have good hardware decoding support.
- Oletros 10y ago> I don't think that they will ever have good hardware decoding support. Almost all modern the GPUs and processors have hardware decoding for VP9
- Godel_unicode 10y ago> The only issue is it's patented and it's bad at encoding compared to VP9/H.265 Your argument is that Google is evil for pushing a codec that's patent-free and better as a codec? Also, as others have stated, VP9 has wide hardware acceleration support (and will have wider support in the future)?