ie8 fix
madison

Hardware 2.0

Adrian Kingsley-Hughes

Chrome's love of WebM and hatred of H.264 has nothing to do with YouTube

By | January 19, 2011, 4:42am PST

The decision of the Google Chrome team to dump support for the H.264 video codec has nothing to do with YouTube, so says Guardian’s Charles Arthur.

How did he come to this conclusion? He asked Google. When asked directly what effect the decision by the Chrome team to drop support for H.264 would have to YouTube, a Google PR representative had this to say:

“The announcement is only about the way video is handled within the Chrome browser. It does not affect YouTube or Android.”

From the long Q&A session that Arthur has with Google, we can tease out the following details;

  • Google is not giving up H.264 on YouTube.
  • H.264 support will continue to be supported in Android.
  • It’s clear that the decision by the Chrome team to remove support for H.264 was down to the Chrome team, and not a high level Google decision.
  • Android and iOS owners aren’t going to see YouTube go dark any time soon.

I agree with Arthur’s conclusion:

In short? It remains one to watch - the effects could be far-ranging, but they’re still some way off. And it confirms, if you needed it confirming, that Google is a bottom-up organisation, driven by its engineers.

It’s now blatantly clear that this issue has nothing to do with YouTube storage issues, H.264 license pricing or Google’s desire to be totally open source - it’s about Chrome wanting to be disruptive.

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Adrian Kingsley-Hughes is an internationally published technology author who has devoted over a decade to helping users get the most from technology.

Disclosure

Adrian Kingsley-Hughes

All opinions expressed on Hardware 2.0 are those of Adrian Kingsley-Hughes. Every effort is made to ensure that the information posted is accurate. If you have any comments, queries or corrections, please contact Adrian via the email link here. Any possible conflicts of interest will be posted below. [Updated: February 23, 2010] - Adrian Kingsley-Hughes has no business relationships, affiliations, investments, or other actual/potential conflicts of interest relating to the content posted so far on this blog.

Biography

Adrian Kingsley-Hughes

Adrian Kingsley-Hughes is an internationally published technology author who has devoted over a decade to helping users get the most from technology -- whether that be by learning to program, building a PC from a pile of parts, or helping them get the most from their new MP3 player or digital camera.

Adrian has authored/co-authored technical books on a variety of topics, ranging from programming to building and maintaining PCs. His most recent books include "Build the Ultimate Custom PC", "Beginning Programming" and "The PC Doctor's Fix It Yourself Guide". He has also written training manuals that have been used by a number of Fortune 500 companies.

Adrian also runs a popular blog under the name The PC Doctor, where he covers a range of computer-related topics -- from security to repairing and upgrading.

36
Comments

Join the conversation!

Just In

RE: Chrome's love of WebM and hatred of H.264 has nothing to do with YouTube
jorjitop 23rd Jan 2011
@lemuelinchrist

"Chrome and Firefox being true open source projects"

Chrome (Google) uses plenty of open source, but Google is not a true open source company. Most of the open source software they absorb and then produce a proprietary version for distribution.
0 Votes
+ -
IE9
IE9 19th Jan 2011
On Ed Bott blog I already calculated that using webM only on Youtube in favor of h.264 could cost a whopping 500 billion Wh in extra energy costs.
So it would not be wise to switch Youtube tot WebM.
0 Votes
+ -
Chrome being disruptive??
lemuelinchrist 19th Jan 2011
"it?s about Chrome wanting to be disruptive."

No, it's about Chrome and Firefox being true open source projects and supporting open formats.

Google is a bottom-up organization. That means the Engineers were the ones making the decision. And what are the chances of Engineers being idealistic?
0 Votes
+ -
Your answer...
wolf_z 19th Jan 2011
@lemuelinchrist

"what are the chances of Engineers being idealistic?"

1. happy As in 100% They're human, after all and as capable of being fanbois for their own team as anyone else.
0 Votes
+ -
"Chrome supports Open Source"
Michael Alan Goff Updated - 19th Jan 2011
Like Flash!
@goff256

...closed source as well, especially something that is so widely used for their main income source...Adverts!
@lemuelinchrist H.264 is a completely open standard... where several companies and anyone can have their say on the format and approved by governing bodies... your statement is completely hypocritical, since Chrome has built in a Closed an proprietary Flash wrapper instead, governed by one company and closed to others that are not on their approved list......

idealist indeed... hypocritical is the word you were looking for.....
@lemuelinchrist

"Chrome and Firefox being true open source projects"

Chrome (Google) uses plenty of open source, but Google is not a true open source company. Most of the open source software they absorb and then produce a proprietary version for distribution.
0 Votes
+ -
Semantics: whatever decisions are made by the "Chrome Team"
Dietrich T. Schmitz, ~ Your Linux Advocate Updated - 19th Jan 2011
are ultimately decisions approved by Google.
Scoping aside.
posturing. I would say that it has at least helped publicize Chrome! It will hopefully keep H.264 out of HTML5 as well.
0 Votes
+ -
Keep h.264 out of html5 indeed!
Dietrich T. Schmitz, ~ Your Linux Advocate 19th Jan 2011
@DonnieBoy
Nt
Why didn't any of the other ZDNet bloggers ask Google directly?
0 Votes
+ -
Probably because . . .
JLHenry 19th Jan 2011
@Loverock Davidson

Most of the time, Companies like Google, MS, Apple, etc., will not say anything outside of their official releases, or refer you to their Marketing dept.

I imagine that most of the bloggers here, simply got used to the status quo, and didn't even think about asking them directly . . .
@Loverock Davidson because no one needed to ask Google directly, it would be stupid to put in a substandard extra encoding for Youtube, when every single hardware device, INCLUDING ANDROID PHONES do or will have hardware decoding of H.264...

it would in otherwords have been idiotic for Google to make YouTube have not only twice the storage needed, but more, because WebM is that less efficient as a video compressor, worse the results of WebM on video are seriously flawed in video playback...

if Google did this, and then required Android phones to use WebM for instance, their battery life would be half what it is... worse after Google finished, the true owners of the tech behind WebM would sue google for millions.. rightly or wrongly, google would be in a court case for years......

Google isn't that stupid. just the Chrome team is.... even their statement was hypocritical, claiming openness while further integrating the proprietary Flash wrapper, which they have to integrate even further because it is a crashing and security nightmare...

so Chrome gave up a superior codec that is an open standard, where everyone can see the code to trade off to a closed proprietary wrapper, where Adobe has to approve your ability to see the code, which they do not do unless you are a partner of Adobe....

anybody seeing how completely ridiculous the Chrome Team was in their statement? atleast claim that they want to forward their own slower tech, that is years behind H.264 atleast, instead of hypocritically playing the "open" free hugger card.
0 Votes
+ -
please help
kleav 19th Jan 2011
I don't understand what this means. Is H264 already supported by flash addon? Is this new codec also supported by flash or will flash not be needed then?
@kleav
Good question. I am also waiting for Google's response on this. But I don't think so, because Chrome directly supports WebM, so having to render it via Flash is moot, but I to don't know how it would become in the final Chrome.
@kleav
The point is that they are removing H.264 support from the direct "video" tag in HTML5, which is a big step away from where the new standard has been going. The idea was to have a standard way to play video without needing a plugin. Google is breaking that.
@A.Sinic, Correct, except chrome is breaking that not google... which will not slow down the video tag, because everyone else that knows what they are doing is using it already....... the only people fighting it is the open source free huggers... believe it or not, they do not matter when money comes calling.

hardware companies are not going to wait, so some free hugger can download more stolen code... they want hardware video encryption now... actually they already are doing the chips with it.. and why your Android phone gets somewhat battery life, so it is atleast somewhat close to an iPhones...... EVERY ONE is using H.264, except the free huggers.... for instance if Android phones used webM, everyone would laugh at their battery life... literally...

the comparison, is every major corp that makes hardware or software, compared to a bunch of basement dwelling no names who still live with their parents...

the decision has already been made, just like MP3 codec, and ACC, and hardware encryption, it is just a bunch of wanna bees crying over their already spilled milk...

no one was holding the HTML5 tag back but them.... now they've made the HTML5 tag decision much easier, because the real companies are now fed up with them.
@kleav Me either. What DOES this mean. This blog and these comments don't bring us any closer.
@kleav

Essentially this is a non issue. What matters to web application creators (like myself) is not having to distribute audio/video in multiple formats. As long as Google supports Flash I'll distribute in H264 and use Flash for rendering or WMP or HTML5 (when it supports H264). All Google is assuring is that conditional code to support different browsers and add-ons will continue to be used.

The real question is why anyone would bother with WebM, a demonstrably inferior codec with no hardware support whose "patent-free" status has yet to be tested.
@tonymcs@... "All Google is assuring is that conditional code to support different browsers and add-ons will continue to be used."

they are also assuring that Chrome has a needless crashy extra security head ache with Flash for a long time to come....

needless unless of course a browser wants those flash ads, the worst thing man has ever created... but for some reason, people claim this is a bad thing that HTML5 can not yet do those horrific ads that interrupt video and obscure it. and those front doors to websites that look like a child designed them......

it is like drop outs who have never seen a piece of art in their life doing video games as an ad or neon flashing website... and useless web games.. god help them.

there is a good reason that "flash" blockers have a brisk business going...
0 Votes
+ -
Chrome is irrelevant
comp_indiana 19th Jan 2011
Chrome is irrelevant, not disruptive.
0 Votes
+ -
Bingo (nt)
fairportfan 19th Jan 2011
nt
@comp_indiana -yeppers
0 Votes
+ -
ditto
sackbut 19th Jan 2011
@comp_indiana
copied the UI for IE9. At 10% market share, Chrome is making a lot of waves.
This is not about being disruptive, this is about open source. If Google wanted to be disruptive, they had that achieved already. They're on a complete rampage of eating up market share.
0 Votes
+ -
Google- we own your time
mswift@... 19th Jan 2011
The first big disrupter from Google was the refusal to handle pages with "frames" properly. If they just painted the new frame it would look awfully bad waiting for new ads. So Google decided we needed an entire new page each time. That makes more ad views and keeps each ad up for a shorter time, so more money for Google and vastly more time and expense for the rest of the world in order to make googols for Google.
0 Votes
+ -
Hadn't noticed
fairportfan 19th Jan 2011
@mswift@... I hadn't noticed that - there are too many other deal-breakers that you hit a lot faster than that with Chrome for me.

Sad, too, because it looked like a Good Idea on paper (as it were).
0 Votes
+ -
...
Fletchguy 19th Jan 2011
Ahhh Chrome sucks. The chrome browser I have found and used for about a year now on fe machines is slow and laggy. Its look well thats just bad too. I don't have much good to say about chrome. I love google and android but chrome looke like it was made by minimalistic retards and functionality is not user friendly. The best browsers are still firefox and Opera.
0 Votes
+ -
Ever since...
fairportfan 19th Jan 2011
...i realised that Chrome installs in a non-standard manner and location, it's been off my list of things i want to use.
0 Votes
+ -
It's about doing evil...
comp_indiana 19th Jan 2011
Goog has lost it's supposed 'roots' I think.
0 Votes
+ -
just like the Verizon told Google what to say on net neutrality - here, they are just being told by Adobe what to say ... Adobe is helping them build the next Android OS.
0 Votes
+ -
Uphill battle
SquishyParts 19th Jan 2011
Google will have an uphill battle if they think this move is going to make WebM the standard.
0 Votes
+ -
Nope, nothing at all.
james347 19th Jan 2011
Dope!
0 Votes
+ -
Open?
SquishyParts 19th Jan 2011
Google! We built a fractured platform that the phone companies control...We're Open!

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix
Click Here
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix
ie8 fix