4 ms·
Yet the number one reason there isn't a codec specified in HTML5 is because Apple blocked it.
by ZeroGravitas 16y ago
Yet the number one reason there isn't a codec specified in HTML5 is because Apple blocked it.
- ZeroGravitas 16y agoAlso, Apple used to be fully behind royalty-free standards for the web: http://lists.w3.org/Archives/Public/www-patentpolicy-comment/2001Oct/1488 http://lists.w3.org/Archives/Public/www-patentpolicy-comment... Apple believes that it is essential to continued interoperability and development of the Web that fundamental W3C standards be available on a royalty-free basis. In line with the W3C's mission to "lead the Web to its full potential," Apple supports a W3C patent policy with an immutable commitment to royalty-free licensing for fundamental Web standards. Apple offers this statement in support of its position. It's powerful and persuasive stuff, worth reading in full. They only removed this statement from their website about 6 months ago.
- extension 16y agoHave they said or done something that conflicts with this statement?
- mbrubeck 16y agoTheir implementations of the HTML5 <video> and <audio> draft standards work only with royalty-encumbered codecs. (The licensing is currently royalty-free for publishers and end users, but not for device manufacturers or browser vendors.)
- extension 16y agoHave they ever proposed that those codecs be part of the standard?
- rmc 16y agoGoogle were also opposed to a format in the spec, they claimed ogg theora was too large in file size. Why do you think they bought On2 and released WebM in the first place? There already was a free video code theora before.
- ubernostrum 16y agoBullshit. Multiple companies, including Apple (and Nokia, which ain't exactly a minor player in the mobile market) objected to HTML5 mandating support for a particular codec, largely on the grounds that we don't really know the patent situations of any of the allegedly-unencumbered codecs. Meanwhile, multiple people objected on the grounds that mandating a current (or, really, several-years-old now since that's what it is) codec in a spec that's not expected to go final for at least a few more years, and which has an expected useful life of around a decade, is just frankly stupid. It'd be like having a spec used today mandate XBM as the standard image format because that was the least-proprietary thing available 15 years ago when early browsers were being written.
- gloob 16y agoMultiple companies, including Apple (and Nokia, which ain't exactly a minor player in the mobile market) objected to HTML5 mandating support for a particular codec, largely on the grounds that we don't really know the patent situations of any of the allegedly-unencumbered codecs. Now it's my turn to call bullshit. "We don't really know the patent situations of $x" could be used as an argument against ANY piece of software or standard $x. Unless there is real evidence for such concerns, it's FUD.
- ubernostrum 16y agoThere ain't no such thing as a free codec. At least, not as long as software patents exist. Does Google want a Free, interoperable web? Then they should take the money they'd spend re-encoding all of YouTube into VP8 and instead spend it on lobbying to eliminate software patents. Then they could just use whatever's the best option from a technical perspective and we could stop having codec shitstorms every six months.
- mbrubeck 16y ago"There ain't no such thing as a free codec." This is what groups like the MPEG-LA want us to think, but I'm not so sure. The Ogg Vorbis codec used for WebM audio has been in use for a decade, and has shipped in dozens of software and hardware products, some from large companies with big pockets. MPEG-LA made the same vague threats about patent pools against Vorbis, but they never followed through. Xiph.org conducted a patent search early in the Vorbis process, and believes Vorbis does not infringe on any patents. Google has done their homework on VP8 as well. If they did it right, then VP8 is no more vulnerable to unknown patent threats than any random piece of software. (Sadly, any random piece of software is somewhat vulnerable.) For that matter, there's no guarantee that H.264 is invulnerable from patent trolls who aren't members of the licensing pool. MPEG-LA doesn't indemnify licensees against third-party patents.
- scottbruin 16y agoThat's false. Read this: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-June/020620.html http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-Jun... MS didn't commmit to anything, Mozilla essentially blocked H.264 from becoming specified codec too. All had reasonably sound reasons to hold their respective position. Not everything can be explained as good vs. evil.