<?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: Not just mobile: Adobe is abandoning Flash on TVs as well</title>
	<atom:link href="http://gigaom.com/2011/11/09/flash-tv-future/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2011/11/09/flash-tv-future/</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 03:43:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Van Melton</title>
		<link>http://gigaom.com/2011/11/09/flash-tv-future/#comment-692143</link>
		<dc:creator><![CDATA[Van Melton]]></dc:creator>
		<pubDate>Thu, 24 Nov 2011 10:20:09 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=436172#comment-692143</guid>
		<description><![CDATA[But pushing #AIR: &quot;Not just mobile: Adobe is abandoning #Flash on TVs as well&quot; http://t.co/QtmSCQaS #RIA]]></description>
		<content:encoded><![CDATA[<p>But pushing #AIR: &quot;Not just mobile: Adobe is abandoning #Flash on TVs as well&quot; <a href="http://t.co/QtmSCQaS" rel="nofollow">http://t.co/QtmSCQaS</a> #RIA</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 소셜캐스터</title>
		<link>http://gigaom.com/2011/11/09/flash-tv-future/#comment-680140</link>
		<dc:creator><![CDATA[소셜캐스터]]></dc:creator>
		<pubDate>Sat, 19 Nov 2011 09:50:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=436172#comment-680140</guid>
		<description><![CDATA[RT @xguru: 어도비의 모바일 플래시포기는 단순히 모바일뿐만이 아니라 TV에서의 플래시도 포기하는것 http://t.co/BNmuqInG 마치 깨진 유리창을 보는것 같군요.]]></description>
		<content:encoded><![CDATA[<p>RT @xguru: 어도비의 모바일 플래시포기는 단순히 모바일뿐만이 아니라 TV에서의 플래시도 포기하는것 <a href="http://t.co/BNmuqInG" rel="nofollow">http://t.co/BNmuqInG</a> 마치 깨진 유리창을 보는것 같군요.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: socialheartbeat</title>
		<link>http://gigaom.com/2011/11/09/flash-tv-future/#comment-679908</link>
		<dc:creator><![CDATA[socialheartbeat]]></dc:creator>
		<pubDate>Sat, 19 Nov 2011 06:11:33 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=436172#comment-679908</guid>
		<description><![CDATA[(11/18/2011) - today&#039;s number #1 #heartbeat http://t.co/LK1uPA19 (via http://t.co/5Tpqs3Gf) #japira]]></description>
		<content:encoded><![CDATA[<p>(11/18/2011) &#8211; today&#8217;s number #1 #heartbeat <a href="http://t.co/LK1uPA19" rel="nofollow">http://t.co/LK1uPA19</a> (via <a href="http://t.co/5Tpqs3Gf" rel="nofollow">http://t.co/5Tpqs3Gf</a>) #japira</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wonderwhy-er</title>
		<link>http://gigaom.com/2011/11/09/flash-tv-future/#comment-675665</link>
		<dc:creator><![CDATA[wonderwhy-er]]></dc:creator>
		<pubDate>Tue, 15 Nov 2011 22:34:28 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=436172#comment-675665</guid>
		<description><![CDATA[I agree, that&#039;s what this move means as future prospect. Flash now is only viable on desktop web in those projects where HTML5 can&#039;t deliver and will not be able to deliver for some time bet it games or some other rich client side multimedia apps.
Its sad that HTML5 can&#039;t quite deliver yet :(]]></description>
		<content:encoded><![CDATA[<p>I agree, that&#8217;s what this move means as future prospect. Flash now is only viable on desktop web in those projects where HTML5 can&#8217;t deliver and will not be able to deliver for some time bet it games or some other rich client side multimedia apps.<br />
Its sad that HTML5 can&#8217;t quite deliver yet :(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Haedo Kao</title>
		<link>http://gigaom.com/2011/11/09/flash-tv-future/#comment-675215</link>
		<dc:creator><![CDATA[Haedo Kao]]></dc:creator>
		<pubDate>Mon, 14 Nov 2011 20:48:56 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=436172#comment-675215</guid>
		<description><![CDATA[Yes, the browser plugin is being dropped, and not the runtime, but not for technical reasons; it&#039;s simply because companies like Adobe don&#039;t want to loose power over the consumer. A browser plugin is more easily replaceable, since after all, the overall framework is being handled by the browser (think Flash plugin to open source HTML5 transition). The runtime is used by stand-alone apps, which, unlike a standard browser, can have a much higher degree of control over the consumer, at the cost of severely limiting our choices.

Chipset manufacturers love the app-based paradigm because they can retain intellectual propery rights over more functions of their chips, selling separate licenses to integrators (DRM, video/audio codecs, HW acceleration). Big media companies also embrace the app-based paradigm because they still believe it can help them reduce piracy, as opposed to delivering content via open source browser standards. And hardware integrators such as the ones that manufacture OTT set-top boxes or smart TVs also adhere to the same paradigm, because they mistakenly think it will give greater power for their platforms.

And who is the one loosing? The consumer. To make a simple comparison, can you imagine what the Internet would have been if the consumers had been forced to download and install an app for each website they wanted to access? Anyone wanting to read this blog, for instance, would have been forced to download and install a &quot;Gigaom App&quot;. And anyone wanting to read any of the external links of the same blog would have been forced to install another &quot;X App&quot; too.

But what&#039;s even more dangerous is that the key element that holds the concept of what the Internet is today would have never existed: search capability. The consumers who had the &quot;Gigaom App&quot; installed would have been able to search -but only within this particular content provider network. 

It&#039;s almost impossible to imagine that the Internet could have become what it is today without the role of browsers and cross-compliant standards like HTML.

This is directly related to Adobe&#039;s latest moves, and also to how big media companies have turned their backs on GoogleTV, because it shows how some traditional market dominators are afraid of loosing control over the consumer.

Adobe realized that if they continued to promote the browser-based paradigm (like they continuously did since their partnership with GoogleTV was announced), the paradigm would one day, inevitably, transition to an open source, cross-compliant standard, like HTML5. Think of all the video websites that are either evaluating HTML5 as an alternative to Flash, or that have completely dropped Flash support. So instead, Adobe now claims that &quot;the right approach to deliver content on televisions is through applications, not a web browsing experience&quot;. The application approach is simply a closed one, where there is little or no cross-compliant standard.

GoogleTV was actually the first OTT project to seriously consider the role of a web-browser for its platform, allowing the consumer to freely choose the content, and even providing an open-source SDK to build channels optimized for OTT, not only compatible with GoogleTV, but with any HTML5 compliant browser. Without a cross-compliant browser experience, and with the burden of forcing the consumer to download and install a stand-alone application per each content provider, the OTT or &quot;connected TV&quot; market will remain as it is today: a highly fragmented technology that fails to promote the creation of new and innovative content (just think what the big players like Netflix, Amazon or Hulu are providing in terms of content: exactly the same that is broadcasted through traditional networks).

The role of a cross-compliant web browser is extremely important for the evolution of OTT television, and the latest Adobe&#039;s announcement should simply force us to question: who needs Flash anyway? Hopefully other manufacturers with more vision than Logitech will understand the importance of the GoogleTV project for the long term, and Google itself will continue to improve the integration between Chrome and Android, replacing Flash with HTML5 + HLS.]]></description>
		<content:encoded><![CDATA[<p>Yes, the browser plugin is being dropped, and not the runtime, but not for technical reasons; it&#8217;s simply because companies like Adobe don&#8217;t want to loose power over the consumer. A browser plugin is more easily replaceable, since after all, the overall framework is being handled by the browser (think Flash plugin to open source HTML5 transition). The runtime is used by stand-alone apps, which, unlike a standard browser, can have a much higher degree of control over the consumer, at the cost of severely limiting our choices.</p>
<p>Chipset manufacturers love the app-based paradigm because they can retain intellectual propery rights over more functions of their chips, selling separate licenses to integrators (DRM, video/audio codecs, HW acceleration). Big media companies also embrace the app-based paradigm because they still believe it can help them reduce piracy, as opposed to delivering content via open source browser standards. And hardware integrators such as the ones that manufacture OTT set-top boxes or smart TVs also adhere to the same paradigm, because they mistakenly think it will give greater power for their platforms.</p>
<p>And who is the one loosing? The consumer. To make a simple comparison, can you imagine what the Internet would have been if the consumers had been forced to download and install an app for each website they wanted to access? Anyone wanting to read this blog, for instance, would have been forced to download and install a &#8220;Gigaom App&#8221;. And anyone wanting to read any of the external links of the same blog would have been forced to install another &#8220;X App&#8221; too.</p>
<p>But what&#8217;s even more dangerous is that the key element that holds the concept of what the Internet is today would have never existed: search capability. The consumers who had the &#8220;Gigaom App&#8221; installed would have been able to search -but only within this particular content provider network. </p>
<p>It&#8217;s almost impossible to imagine that the Internet could have become what it is today without the role of browsers and cross-compliant standards like HTML.</p>
<p>This is directly related to Adobe&#8217;s latest moves, and also to how big media companies have turned their backs on GoogleTV, because it shows how some traditional market dominators are afraid of loosing control over the consumer.</p>
<p>Adobe realized that if they continued to promote the browser-based paradigm (like they continuously did since their partnership with GoogleTV was announced), the paradigm would one day, inevitably, transition to an open source, cross-compliant standard, like HTML5. Think of all the video websites that are either evaluating HTML5 as an alternative to Flash, or that have completely dropped Flash support. So instead, Adobe now claims that &#8220;the right approach to deliver content on televisions is through applications, not a web browsing experience&#8221;. The application approach is simply a closed one, where there is little or no cross-compliant standard.</p>
<p>GoogleTV was actually the first OTT project to seriously consider the role of a web-browser for its platform, allowing the consumer to freely choose the content, and even providing an open-source SDK to build channels optimized for OTT, not only compatible with GoogleTV, but with any HTML5 compliant browser. Without a cross-compliant browser experience, and with the burden of forcing the consumer to download and install a stand-alone application per each content provider, the OTT or &#8220;connected TV&#8221; market will remain as it is today: a highly fragmented technology that fails to promote the creation of new and innovative content (just think what the big players like Netflix, Amazon or Hulu are providing in terms of content: exactly the same that is broadcasted through traditional networks).</p>
<p>The role of a cross-compliant web browser is extremely important for the evolution of OTT television, and the latest Adobe&#8217;s announcement should simply force us to question: who needs Flash anyway? Hopefully other manufacturers with more vision than Logitech will understand the importance of the GoogleTV project for the long term, and Google itself will continue to improve the integration between Chrome and Android, replacing Flash with HTML5 + HLS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: billsheppard2</title>
		<link>http://gigaom.com/2011/11/09/flash-tv-future/#comment-674328</link>
		<dc:creator><![CDATA[billsheppard2]]></dc:creator>
		<pubDate>Sat, 12 Nov 2011 01:19:26 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=436172#comment-674328</guid>
		<description><![CDATA[Java will remain the major player in this space.  It&#039;s under the covers in every Blu-ray Disc player and many cable and broadcast set-top boxes.  While it doesn&#039;t offer the UI ease-of-development which Flash does/did, it&#039;s got a more flexible architecture which is proving particularly valuable where you want to provide connectivity to a second screen (e.g. tablet or smartphone), where a Java-based DLNA media server or web server can serve up content.]]></description>
		<content:encoded><![CDATA[<p>Java will remain the major player in this space.  It&#8217;s under the covers in every Blu-ray Disc player and many cable and broadcast set-top boxes.  While it doesn&#8217;t offer the UI ease-of-development which Flash does/did, it&#8217;s got a more flexible architecture which is proving particularly valuable where you want to provide connectivity to a second screen (e.g. tablet or smartphone), where a Java-based DLNA media server or web server can serve up content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nikato Muirhead</title>
		<link>http://gigaom.com/2011/11/09/flash-tv-future/#comment-673870</link>
		<dc:creator><![CDATA[Nikato Muirhead]]></dc:creator>
		<pubDate>Thu, 10 Nov 2011 20:09:18 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=436172#comment-673870</guid>
		<description><![CDATA[The next step will be to abandon flash on PC&#039;s and Macs, you wait and see.!!! 
Steve Jobs is dancing in his grave. 
Macs will be crash-free again. !!!]]></description>
		<content:encoded><![CDATA[<p>The next step will be to abandon flash on PC&#8217;s and Macs, you wait and see.!!!<br />
Steve Jobs is dancing in his grave.<br />
Macs will be crash-free again. !!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tv dev</title>
		<link>http://gigaom.com/2011/11/09/flash-tv-future/#comment-673808</link>
		<dc:creator><![CDATA[tv dev]]></dc:creator>
		<pubDate>Thu, 10 Nov 2011 17:04:44 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=436172#comment-673808</guid>
		<description><![CDATA[I think there are some nuances getting lost here. Flash on a TV exists as either: a standalone runtime or a browser plug-in. It sounds like they are dropping the plug-in not the runtime.]]></description>
		<content:encoded><![CDATA[<p>I think there are some nuances getting lost here. Flash on a TV exists as either: a standalone runtime or a browser plug-in. It sounds like they are dropping the plug-in not the runtime.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ignacio Iribarne</title>
		<link>http://gigaom.com/2011/11/09/flash-tv-future/#comment-673776</link>
		<dc:creator><![CDATA[Ignacio Iribarne]]></dc:creator>
		<pubDate>Thu, 10 Nov 2011 15:10:45 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=436172#comment-673776</guid>
		<description><![CDATA[It&#039;s curious that this comes at a time when GoogleTV recently announced a major update to Android 3.1, which unlike the previous GoogleTV v1 (Android 2.1), now has native support for HLS (HTTP Live Streaming), the open source protocol that Apple created to replace Flash for video streaming on all iOS devices... Is it just coincidence that while GoogleTV was running v1, and the only way of delivering live video within the browser was using Flash, Adobe stated:

&quot;The digital home is a huge step for Flash and it represents an amazing new screen for developers and content creators to bring rich interactive content to the TV.&quot;

http://blogs.adobe.com/flashplatform/2010/05/flash_player_101_on_google_tv.html

And now that GoogleTV does have a solid alternative, and it&#039;s actually the same alternative that Apple used from the beginning (and probably an alternative other vendors will use too), Adobe states:

&quot;However we believe the right approach to deliver content on televisions is through applications, not a web browsing experience&quot;

Perhaps we should read between the lines... Adobe is basically saying: if our Flash platform is the only available option, then the future of connected TVs is Flash; if an alternative to Flash (specially one created by Apple) comes in place, then Flash is dead, the browser for connected TVs is dead, and we should all start developing apps instead -using Adobe AIR, of course!]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s curious that this comes at a time when GoogleTV recently announced a major update to Android 3.1, which unlike the previous GoogleTV v1 (Android 2.1), now has native support for HLS (HTTP Live Streaming), the open source protocol that Apple created to replace Flash for video streaming on all iOS devices&#8230; Is it just coincidence that while GoogleTV was running v1, and the only way of delivering live video within the browser was using Flash, Adobe stated:</p>
<p>&#8220;The digital home is a huge step for Flash and it represents an amazing new screen for developers and content creators to bring rich interactive content to the TV.&#8221;</p>
<p><a href="http://blogs.adobe.com/flashplatform/2010/05/flash_player_101_on_google_tv.html" rel="nofollow">http://blogs.adobe.com/flashplatform/2010/05/flash_player_101_on_google_tv.html</a></p>
<p>And now that GoogleTV does have a solid alternative, and it&#8217;s actually the same alternative that Apple used from the beginning (and probably an alternative other vendors will use too), Adobe states:</p>
<p>&#8220;However we believe the right approach to deliver content on televisions is through applications, not a web browsing experience&#8221;</p>
<p>Perhaps we should read between the lines&#8230; Adobe is basically saying: if our Flash platform is the only available option, then the future of connected TVs is Flash; if an alternative to Flash (specially one created by Apple) comes in place, then Flash is dead, the browser for connected TVs is dead, and we should all start developing apps instead -using Adobe AIR, of course!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vin Hennessy</title>
		<link>http://gigaom.com/2011/11/09/flash-tv-future/#comment-673742</link>
		<dc:creator><![CDATA[Vin Hennessy]]></dc:creator>
		<pubDate>Thu, 10 Nov 2011 12:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=436172#comment-673742</guid>
		<description><![CDATA[Steve Job was right. He didn&#039;t allow Flash to run on iPhone, etc.]]></description>
		<content:encoded><![CDATA[<p>Steve Job was right. He didn&#8217;t allow Flash to run on iPhone, etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
