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 457794
To read all comments associated with this story, please click here.
H264 not like GIF
by jrincayc on Fri 14th Jan 2011 04:10 UTC
jrincayc
Member since:
2007-07-24

The linked article states "But all the while, GIF was widely used across the web, and there's no real sense that the web was held back by the GIF patents."

GIF images could be freely decoded, which is a huge difference. Encoding was the only part that was patented. Since decoding was patent free, legal open source decoders could be written. So in the GIF case, legal open source browsers could be written that displayed the images. With H264, decoding is patented, so legal open source browsers cannot be written that display the images.

Reply Score: 2