Linked by Thom Holwerda on Thu 13th Jan 2011 06:32 UTC
Internet & Networking "The promise of HTML5's video tag was a simple one: to allow web pages to contain embedded video without the need for plugins. With the decision to remove support for the widespread H.264 codec from future versions of Chrome, Google has undermined this widely-anticipated feature. The company is claiming that it wants to support 'open codecs' instead, and so from now on will support only two formats: its own WebM codec, and Theora." Sorely disappointed in Ars' Peter Bright. Us geeks reviled web developers for sticking to Internet Explorer when Firefox came onto the scene, and yet now, the same arguments we used to revile are used to keep H.264 in the saddle. How us mighty geeks have fallen.
Permalink for comment 458086
To read all comments associated with this story, please click here.
jrincayc
Member since:
2007-07-24

I agree with you in your context that MP3 should not be part of the standards for the web until decoding and encoding can be freely done. I think that there is less motivation for Google to remove the MP3 decoder than things like AAC and H264.

I am guessing that once MP3 decoding is royalty free, it should be possible to make a MP3 encoder, but it may be a pretty bad one. The other year that is mentioned is 2017.

Reply Parent Score: 1