Luckily it's going to be W3C standard, and Apple and MS won't be able to use their lame excuses to avoid implementing it in their browsers, like they did for Vorbis, VP8 and etc.
Where is Google in all this? They must surely be aware of all such IETF projects. I can understand why Apple wasn't mentioned (Apple Island is a world unto itself to the maximum extent possible), but Google has usually pursued the opposite strategy. This seems like the sort of thing they would get behind unless there is some issue I'm unaware of, and it seems as though Mozilla would mention Google in this infomercial if they were backing it.
I went into the article thinking why isn't OGG good enough, and the xkcd joke about 15 different standards.<p>I left pleased about this new standard (from an advert, any downsides?) but need some patent assurances. If Mozilla are happy will everyone be?
I understand they were trying to finalize the spec and weren't worried too much about the individual encoder decisions, but check out some of the code at the bottom of this convo, it's scary <a href="http://pbox.ca/16cbg" rel="nofollow">http://pbox.ca/16cbg</a>