Linked by Thom Holwerda on Tue 11th Jan 2011 22:21 UTC, submitted by Kroc
Google The WebM project - a VP8 video stream and a Vorbis audio stream wrapped in a Matroska container re-branded as a WebM container - launched by Google, openly supported by every major chip maker, is going to be the major codec for Google's Chrome web browser. Yes, Google is dropping H264 support from the Chrome web browser.
Thread beginning with comment 457099
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

"Those companies that will be denied patent royalties as a result of Google's actions are in a position to file suit in the EU."

That kinda makes it sound like these companies in the h264 patent pool have a god given right to force the world to pay them patent royalties.

Sorry, Google has no obligation whatsoever to support h264, nor do content providers, nor do users. h264, while it might arguably have greater technical merits at the moment, is a codec that has, in fact, been forced on users and content providers by Apple and Microsoft and MPEG-LA.

Now, if h264 is offered as a choice, and it competes on technical merits, then I would have no problem using it, and I would happily pay for it, if it's technical merits did indeed make it worth the price.

But an "open" web should always default to open codecs/standards, and not patent encumbered ones.

Let those companies in the MPEG-LA patent pool earn their patent royalties.

Reply Parent Score: 9