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.
Browser war is over. We now see the Codec war ...
That's bad news for all video publishers and video consumers.
I hope this backfires for them. I do not care about the implications for the companies, I care for the users and I would personally hope this turns out to be a mistake for Google. Can't help it, fight your stupid wars elsewhere. I want it to work, and do not care how it works - it just has to work. I would even use Flash for crying out loud.
Disclaimers apply, and YMMV.
The discrepancy between what is written and what is said is awesome on that one. Obnoxious.
Maybe you guys need some further reading on this matter.
as our goal is to enable open innovation
Will they drop the bundled, proprietary, flash player as well?
Simon says ...
I like this. Very clever move. H.264 patent restrictions makes it too dangerous to support.
The mess with H.264 licensing
Think built-in hardware decode support for h.264. This translates into less of a drain on mobilie device battery life, console efficiency (can a tiny device like the AppleTV , etc. Everyone is still going to need to generate h.264, so this just adds more work for the content generators. They would need to generate h.264 and WebM, or only generate h.264, serve it straight to browsers that support it, and serve it via Flash to those that don't.
@Kevan, see this long, but German response to your argument.
Jochen Kattoll on COBO - you are going to hear this at 00:40
Andrew Magerman on Apple Music on SONOS :: How soon is ASAP? at 23:37
Kevan Emmott on Apple Music on SONOS :: How soon is ASAP? at 22:45
Max Nierbauer on Microsoft could write off billions on Nokia deal at 22:34
Jörg Michael on Apple Watch Sapphire vs Glass Display Shoot-Out at 16:23
David Eyre on Umgekehrte Alex-Warnung at 23:46
Volker Weber on Umgekehrte Alex-Warnung at 22:06
David Eyre on Umgekehrte Alex-Warnung at 21:58
Volker Weber on Earn your breakfast at 17:36
Craig Wiseman on Apple Music on SONOS :: How soon is ASAP? at 15:55
Frank Koehntopp (@koehntopp) on Withings imports from Fitbit at 15:31
Kai Bode on Earn your breakfast at 14:41
John Lindsay on Earn your breakfast at 14:31
Jochen Kattoll on Earn your breakfast at 13:57
Ralph Hammann on Earn your breakfast at 12:28
Mariano kamp on Earn your breakfast at 12:04
Dragon Cotterill on Earn your breakfast at 11:36
Kristof Doffing on Introducing Atom 1.0 at 10:09
Kai Bode on Earn your breakfast at 10:05
Volker Weber on Apple Music on SONOS :: How soon is ASAP? at 09:51
Jens Nullmeyer on Apple Music on SONOS :: How soon is ASAP? at 09:42
Pieterjan Lansbergen on Earn your breakfast at 02:36
Volker Weber on Umgekehrte Alex-Warnung at 22:34
Heiko Müller on Umgekehrte Alex-Warnung at 21:55
Markus Dierker on Apple Music on SONOS :: How soon is ASAP? at 21:52