<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Chrome Dropping H.264 Support Is Irrelevant &#8212; Here&#8217;s Why</title>
	<atom:link href="http://gigaom.com/2011/02/04/jw-chrome-h264-webm/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2011/02/04/jw-chrome-h264-webm/</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 05:14:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Keyword</title>
		<link>http://gigaom.com/2011/02/04/jw-chrome-h264-webm/#comment-608907</link>
		<dc:creator><![CDATA[Keyword]]></dc:creator>
		<pubDate>Tue, 15 Mar 2011 16:42:59 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=293860#comment-608907</guid>
		<description><![CDATA[As Google transits to WebM they will be in a position for some Microsoft style sandbagging. They don&#039;t need to drop H.264 to injure iPhone/iPad attractiveness. All they need to do is not put any effort into doing h.264 well. They can make sure they do a poor job of transcoding to H.264, while busting a gut to improve VP8 encoding quality. Eventually, with 50% of web video looking crappy on iOS, Android phones &amp; tablets score a big win. And good luck going to court and trying to prove they&#039;re not trying &quot;hard enough&quot;.]]></description>
		<content:encoded><![CDATA[<p>As Google transits to WebM they will be in a position for some Microsoft style sandbagging. They don&#8217;t need to drop H.264 to injure iPhone/iPad attractiveness. All they need to do is not put any effort into doing h.264 well. They can make sure they do a poor job of transcoding to H.264, while busting a gut to improve VP8 encoding quality. Eventually, with 50% of web video looking crappy on iOS, Android phones &amp; tablets score a big win. And good luck going to court and trying to prove they&#8217;re not trying &#8220;hard enough&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JeroenW</title>
		<link>http://gigaom.com/2011/02/04/jw-chrome-h264-webm/#comment-588014</link>
		<dc:creator><![CDATA[JeroenW]]></dc:creator>
		<pubDate>Mon, 07 Feb 2011 18:35:47 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=293860#comment-588014</guid>
		<description><![CDATA[I&#039;m flattered this article gets its share of  &quot;Flash must die&quot;, &quot;Flash is a relic&quot; and &quot;Flash is a thing of the past&quot; comments. It was besides the point though. 

The point was that, because of Flash, desktop browser vendors will not be deciding whether WebM or H264 will prevail. It&#039;s on devices where Flash is not available (or working poorly) that the vendors will be able to make a difference. No video publisher cares Chrome is now WebM only. If Android is to become WebM only, publishers will start encoding to WebM.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m flattered this article gets its share of  &#8220;Flash must die&#8221;, &#8220;Flash is a relic&#8221; and &#8220;Flash is a thing of the past&#8221; comments. It was besides the point though. </p>
<p>The point was that, because of Flash, desktop browser vendors will not be deciding whether WebM or H264 will prevail. It&#8217;s on devices where Flash is not available (or working poorly) that the vendors will be able to make a difference. No video publisher cares Chrome is now WebM only. If Android is to become WebM only, publishers will start encoding to WebM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JeroenW</title>
		<link>http://gigaom.com/2011/02/04/jw-chrome-h264-webm/#comment-587659</link>
		<dc:creator><![CDATA[JeroenW]]></dc:creator>
		<pubDate>Mon, 07 Feb 2011 08:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=293860#comment-587659</guid>
		<description><![CDATA[I see the &quot;Youtube switch&quot; argument a lot, but I don&#039;t really buy it. If Google flips the switch on Youtube, the one company that will feel most pain is Youtube itself. All video advertising in the world is Flash and all non-desktop devices do only H264. Youtube would be left without revenue and without device penetration. 

Also, Youtube is not as sticky as a Facebook or Twitter. When Youtube puts in effect changes that will make it less interesting (like not working on mobile devices), people might switch to sites like Facebook and Vimeo for their uploads. 

That&#039;s not to say Google is a smart company and Youtube is a huge asset. I&#039;m sure they will find ways to push adoption of WebM, but it won&#039;t be an overnight switch. Let&#039;s first wait and see what happens in the areas of WebM hardware support and Flash VP8 support.]]></description>
		<content:encoded><![CDATA[<p>I see the &#8220;Youtube switch&#8221; argument a lot, but I don&#8217;t really buy it. If Google flips the switch on Youtube, the one company that will feel most pain is Youtube itself. All video advertising in the world is Flash and all non-desktop devices do only H264. Youtube would be left without revenue and without device penetration. </p>
<p>Also, Youtube is not as sticky as a Facebook or Twitter. When Youtube puts in effect changes that will make it less interesting (like not working on mobile devices), people might switch to sites like Facebook and Vimeo for their uploads. </p>
<p>That&#8217;s not to say Google is a smart company and Youtube is a huge asset. I&#8217;m sure they will find ways to push adoption of WebM, but it won&#8217;t be an overnight switch. Let&#8217;s first wait and see what happens in the areas of WebM hardware support and Flash VP8 support.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JeroenW</title>
		<link>http://gigaom.com/2011/02/04/jw-chrome-h264-webm/#comment-587655</link>
		<dc:creator><![CDATA[JeroenW]]></dc:creator>
		<pubDate>Mon, 07 Feb 2011 08:10:18 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=293860#comment-587655</guid>
		<description><![CDATA[I might be a bit too optimistic about WebM indeed, but at the same time it would be good to have free baseline codec on the web. Hopefully it&#039;s not too wishful thinking. As I said though, there&#039;s still much to be done for WebM. 

Apple&#039;s HLS is indeed something that works closely with HTML5, but it is not HTML5. It&#039;s only supported on Apple devices. And I&#039;m not aware of any adaptive streaming support in either WinPho7 (they don&#039;t even support a plain  tag) or Android 3.0. Do you have links to pages that make these statements?]]></description>
		<content:encoded><![CDATA[<p>I might be a bit too optimistic about WebM indeed, but at the same time it would be good to have free baseline codec on the web. Hopefully it&#8217;s not too wishful thinking. As I said though, there&#8217;s still much to be done for WebM. </p>
<p>Apple&#8217;s HLS is indeed something that works closely with HTML5, but it is not HTML5. It&#8217;s only supported on Apple devices. And I&#8217;m not aware of any adaptive streaming support in either WinPho7 (they don&#8217;t even support a plain  tag) or Android 3.0. Do you have links to pages that make these statements?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://gigaom.com/2011/02/04/jw-chrome-h264-webm/#comment-587645</link>
		<dc:creator><![CDATA[James]]></dc:creator>
		<pubDate>Mon, 07 Feb 2011 07:26:25 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=293860#comment-587645</guid>
		<description><![CDATA[This story is not accurate and must be mistaken not and this very screwed. View side low self esteem bigot. Flash is limit and old technology.  HTML5 is plenty leap ahead in current and future.  I am not fan of Flash!  Flash is not effective as what I was expecting!]]></description>
		<content:encoded><![CDATA[<p>This story is not accurate and must be mistaken not and this very screwed. View side low self esteem bigot. Flash is limit and old technology.  HTML5 is plenty leap ahead in current and future.  I am not fan of Flash!  Flash is not effective as what I was expecting!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://gigaom.com/2011/02/04/jw-chrome-h264-webm/#comment-587572</link>
		<dc:creator><![CDATA[Ben]]></dc:creator>
		<pubDate>Mon, 07 Feb 2011 01:37:06 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=293860#comment-587572</guid>
		<description><![CDATA[Google owns youtube, Google owns webm, google wins due to youtubes monopoly]]></description>
		<content:encoded><![CDATA[<p>Google owns youtube, Google owns webm, google wins due to youtubes monopoly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Snafu</title>
		<link>http://gigaom.com/2011/02/04/jw-chrome-h264-webm/#comment-587553</link>
		<dc:creator><![CDATA[Snafu]]></dc:creator>
		<pubDate>Sun, 06 Feb 2011 23:37:43 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=293860#comment-587553</guid>
		<description><![CDATA[Things are a bit more complex that they seem. Google can&#039;t include h.264 decoding in Chrome for the same reasons Mozilla can&#039;t: it breaks its &quot;open-sourceness&quot;. Certainly, it can be introduced back via the host OS&#039; multimedia architecture, but then that&#039;s something not all OSes can do because of licensing reasons.

Also, h.264 can&#039;t become the default HTML5 video codec, anyway, because patent-encumbered technologies aren&#039;t allowed in the standard. At most it can become supported, though not required.

WebM is being proposed as a royaltie-free baseline video codec. My interpretation is that WebM ought to be a fallback codec, so systems that won&#039;t admit h.264 or others because of their license issues (that means all Linuxes, for a start) can play video content, anyway. Given that the h.264 license imposes severe restrictions in distribution, and the conditiions are to change in the future, a by-default royaltie-free codec would be in our best interests. Google is favoring that by converting Youtube&#039;s library to WebM too, and they say they don&#039;t intend to delete their h.264 content at all.

(The interesting thing to see happen would be Adobe integrating WebM in Flash, as they are the ones paying the h.264 royalties Flash video incurs)]]></description>
		<content:encoded><![CDATA[<p>Things are a bit more complex that they seem. Google can&#8217;t include h.264 decoding in Chrome for the same reasons Mozilla can&#8217;t: it breaks its &#8220;open-sourceness&#8221;. Certainly, it can be introduced back via the host OS&#8217; multimedia architecture, but then that&#8217;s something not all OSes can do because of licensing reasons.</p>
<p>Also, h.264 can&#8217;t become the default HTML5 video codec, anyway, because patent-encumbered technologies aren&#8217;t allowed in the standard. At most it can become supported, though not required.</p>
<p>WebM is being proposed as a royaltie-free baseline video codec. My interpretation is that WebM ought to be a fallback codec, so systems that won&#8217;t admit h.264 or others because of their license issues (that means all Linuxes, for a start) can play video content, anyway. Given that the h.264 license imposes severe restrictions in distribution, and the conditiions are to change in the future, a by-default royaltie-free codec would be in our best interests. Google is favoring that by converting Youtube&#8217;s library to WebM too, and they say they don&#8217;t intend to delete their h.264 content at all.</p>
<p>(The interesting thing to see happen would be Adobe integrating WebM in Flash, as they are the ones paying the h.264 royalties Flash video incurs)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon T</title>
		<link>http://gigaom.com/2011/02/04/jw-chrome-h264-webm/#comment-587477</link>
		<dc:creator><![CDATA[Jon T]]></dc:creator>
		<pubDate>Sun, 06 Feb 2011 17:05:30 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=293860#comment-587477</guid>
		<description><![CDATA[Nothing in this post convinces anyone that Flash is here to stay. 

Flash is on the way out. In two years it will be a relic.]]></description>
		<content:encoded><![CDATA[<p>Nothing in this post convinces anyone that Flash is here to stay. </p>
<p>Flash is on the way out. In two years it will be a relic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DW</title>
		<link>http://gigaom.com/2011/02/04/jw-chrome-h264-webm/#comment-587346</link>
		<dc:creator><![CDATA[DW]]></dc:creator>
		<pubDate>Sun, 06 Feb 2011 06:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=293860#comment-587346</guid>
		<description><![CDATA[I haven&#039;t gone to the extent of de-friending the people who invite me to Farmville, Fishville, etc., but I&#039;ve turned down every one of their invitations on two grounds: (1) I don&#039;t want Facebook apps getting full access to the information I have marked &quot;friends only&quot; and (2) I refuse play Flash games.

I have a Flash blocker for Camino, ClicktoFlash for Safari and get an increasing amount of information from Twitter and iOS apps. Most video worth watching is available in an iOS compatible format. Paid premium content can be locked using paid apps, but I don&#039;t pay for video on the internet anyway.

As for Flash based advertising and Flash based website navigation I have just three characters: die

Any site that makes me enable Flash just to view their content is a site that doesn&#039;t want my business. As a consumer my voice is my wallet and I let it speak loud and clear.

h.264 is an efficient format that yields nice looking results. If WebM can deliver the same quality with the same efficiency then it wouldn&#039;t be the end of the world to have a gradual switch. It took years for h.264 to become entrenched so it would take years to switch everyone to WebM. From what I&#039;ve heard, however, WebM yields slightly poorer results so it looks like a backwards step that only benefits Google and Mozilla. Not many backward steps ever succeed.]]></description>
		<content:encoded><![CDATA[<p>I haven&#8217;t gone to the extent of de-friending the people who invite me to Farmville, Fishville, etc., but I&#8217;ve turned down every one of their invitations on two grounds: (1) I don&#8217;t want Facebook apps getting full access to the information I have marked &#8220;friends only&#8221; and (2) I refuse play Flash games.</p>
<p>I have a Flash blocker for Camino, ClicktoFlash for Safari and get an increasing amount of information from Twitter and iOS apps. Most video worth watching is available in an iOS compatible format. Paid premium content can be locked using paid apps, but I don&#8217;t pay for video on the internet anyway.</p>
<p>As for Flash based advertising and Flash based website navigation I have just three characters: die</p>
<p>Any site that makes me enable Flash just to view their content is a site that doesn&#8217;t want my business. As a consumer my voice is my wallet and I let it speak loud and clear.</p>
<p>h.264 is an efficient format that yields nice looking results. If WebM can deliver the same quality with the same efficiency then it wouldn&#8217;t be the end of the world to have a gradual switch. It took years for h.264 to become entrenched so it would take years to switch everyone to WebM. From what I&#8217;ve heard, however, WebM yields slightly poorer results so it looks like a backwards step that only benefits Google and Mozilla. Not many backward steps ever succeed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nik</title>
		<link>http://gigaom.com/2011/02/04/jw-chrome-h264-webm/#comment-587281</link>
		<dc:creator><![CDATA[Nik]]></dc:creator>
		<pubDate>Sun, 06 Feb 2011 01:17:56 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=293860#comment-587281</guid>
		<description><![CDATA[Of course it&#039;s symbolic. But it carries the threat that Google might switch YouTube - owned by Google - to WebM/Flash instead of H.264/Flash. 

I think Google can leverage YouTube - Google controls 50% of online video, or more on that alone, and Google could in theory overnight flip a switch and make it all WebM - desktop users would still use Flash so they wouldn&#039;t notice the difference; mobile users would not be able to see it unless they have WebM. There&#039;s plenty of options - a gradual switchover within 2 years for example - would give Google time to do the actual encoding which is no trivial task. And it would put the squeeze on iOS to support WebM. 

I am not sure Google is concerned about H.264 patents so much - after all they have plenty of cash to pay any license fees. But I think they might use it to give Android a boost over iOS. If Google aims for Android adoption then they&#039;ll also entice hardware makers to produce hardware decoders for WebM. It&#039;s a bit of a long term play and it will be interesting to see if Google can pull it off - we&#039;re talking 5 years here. 

This is a chess game between Google and Apple, with Adobe and Microsoft on the sidelines. I don&#039;t think anyone of these players think about desktops right now - it&#039;s all about mobile: Tablets and phones. That&#039;s where all the potential is, and where all the growth is.]]></description>
		<content:encoded><![CDATA[<p>Of course it&#8217;s symbolic. But it carries the threat that Google might switch YouTube &#8211; owned by Google &#8211; to WebM/Flash instead of H.264/Flash. </p>
<p>I think Google can leverage YouTube &#8211; Google controls 50% of online video, or more on that alone, and Google could in theory overnight flip a switch and make it all WebM &#8211; desktop users would still use Flash so they wouldn&#8217;t notice the difference; mobile users would not be able to see it unless they have WebM. There&#8217;s plenty of options &#8211; a gradual switchover within 2 years for example &#8211; would give Google time to do the actual encoding which is no trivial task. And it would put the squeeze on iOS to support WebM. </p>
<p>I am not sure Google is concerned about H.264 patents so much &#8211; after all they have plenty of cash to pay any license fees. But I think they might use it to give Android a boost over iOS. If Google aims for Android adoption then they&#8217;ll also entice hardware makers to produce hardware decoders for WebM. It&#8217;s a bit of a long term play and it will be interesting to see if Google can pull it off &#8211; we&#8217;re talking 5 years here. </p>
<p>This is a chess game between Google and Apple, with Adobe and Microsoft on the sidelines. I don&#8217;t think anyone of these players think about desktops right now &#8211; it&#8217;s all about mobile: Tablets and phones. That&#8217;s where all the potential is, and where all the growth is.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
