Specifying codecs for the web
Specifying codecs for the web
Posted Dec 12, 2007 18:11 UTC (Wed) by nim-nim (subscriber, #34454)Parent article: Specifying codecs for the web
As mp3 proved, having a widely available codec is effectively game over for competitors even if they are technically superior (and in this particular case only theora is a bit weak technically). So the original wording had the potential to vaporise the huge investment companies like Apple and Nokia made in software or hardware implementations of proprietary codecs. It does not matter if those codecs are better technically (and for sound they are not). Making ogg vorbis/theora a public default (even if it's optional) would marginalize them at once. All the carefully built closed gardens and associated revenue streams would suddenly lose their consumer appeal. Companies like Apple and Nokia bet on codecs that could only win over similarly legaly encumbered alternatives, now that WHATWG threatens to call the race end with Ogg Theora/Vorbis in they are frantically trying to preserve the status-quo. Submarine patents are a problem but they affect every codec and forestalling standardization because of them is only good for entities with no interest in standards.
