Google kills H.264 in Chrome | Opensource.com
Google kills H.264 in Chrome
The Internet reacted to yesterday's post on the Chromium blog with astounding speed. What caused the hubbub?
We expect even more rapid innovation in the web media platform in the coming year and are focusing our investments in those technologies that are developed and licensed based on open web principles. To that end, we are changing Chrome’s HTML5 <video> support to make it consistent with the codecs already supported by the open Chromium project. Specifically, we are supporting the WebM (VP8) and Theora video codecs, and will consider adding support for other high-quality open codecs in the future. Though H.264 plays an important role in video, as our goal is to enable open innovation, support for the codec will be removed and our resources directed towards completely open codec technologies.
And since so much has already been said on the matter, I'm simply offering a roundup of what's already been written.
- If you're unfamiliar with the situation and want to get up to speed, start with TechCrunch: The Gloves Are Off: Google Chrome Browser Will Drop Support For H.264 Video Codec
- TNW talks about what it means for the average user.
- John Gruber has a few standing questions about the issue.
- Wondering what other companies think? Opera agrees. Microsoft blogged a slightly snarky but amusing analogy involving Esperanto and Klingon. I don't think the analogy really holds up, but it's the funniest commentary you'll read on the matter.
- A ZDNet blogger called it the ruin of the Chrome browser.
- Joe Brockmeier calls it good news for the open web, bad news for those living through the battle, and asks whether Google and Mozilla can kill H.264.
And to conclude, my favorite of the commentary. Simon Phipps tells everyone to relax, calling "this bold move...another step towards an end to the Flash monopoly on rich media" (Google and H.264 - Far From Hypocritical).