2 ms·
HTML is a web technology, but video codecs are needed by a wider range of applications, including playing optical media, games, and presentation software. The
by wtallis 16y ago
HTML is a web technology, but video codecs are needed by a wider range of applications, including playing optical media, games, and presentation software.
The non-political arguments the mozillazine article makes against using the OS's media frameworks can be solved by using ffmpeg/etc. as fallbacks, except for the one about having to support multiple rendering paths (and even that could be solved by just packaging ffmpeg in the OS-supported codec format).
If a web browser maker wants to make it hard to use H.264 even when the user already has a fully-licensed decoder as part of their operating system, then they are putting their political goals above the users' needs.
If I want my browser to supplant my operating system, I'll use ChromeOS. Otherwise, I want my browser to play nice and not bring along political baggage.
I don't want my browser to include it's own unoptimized codecs, it's own half-assed OpenGL implementation, it's own font rendering code, it's own widget library, it's own PDF viewer, and it's own device drivers. I want my browser to include a kick-ass [X]HTML+CSS+JS engine, and delegate the rest to the operating system like any sane application.
- ootachi 16y agoffmpeg is patent encumbered. If "just ship ffmpeg" were an option, then this wouldn't be an issue in the first place.
- wtallis 16y agoThat doesn't really matter. There's basically no usability difference between: "You need to install plugin X to view this video." "You need to install QuickTime Component X to view this video." "You need to install third-party Firefox codec X to view this video." Except that the third piece of software likely won't exist, and Mozilla might not even let it exist. If browser vendors make it hard to install and use a codec for patent-encumbered formats like H.264, that will only prolong the use of even worse plugins like Flash for the purpose of playing H.264 videos.
- sid0 16y agoHTML is a web technology, but video codecs are needed by a wider range of applications, including playing optical media, games, and presentation software. But inside the browser it's a web technology. That's the whole point of the video tag. When a browser's raison d'être is "political" as you put it, then of course any such decision is going to have a moral component. It isn't just about short-term support -- it's about a long-term vision for what the web should be like, and more importantly shouldn't be like. H.264 isn't compatible with that vision. they are putting their political goals above the users' needs. But those goals are the users' long-term needs. The minor loss if people can't play H.264 video right now is offset by the much greater victory if the web stays free and open. I don't want my browser to include it's own unoptimized codecs, it's own half-assed OpenGL implementation, it's own font rendering code, it's own widget library, it's own PDF viewer, and it's own device drivers. Stop making ridiculous blanket statements. This is much more nuanced than that, and involves balancing the costs of including custom code with its benefits.