<?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/"
		>
<channel>
	<title>Comments on: Warning Signs &#8216;Flash&#8217;ing for Adobe</title>
	<atom:link href="http://stocktwitstech.com/warning-signs-flashing-for-adobe/feed/" rel="self" type="application/rss+xml" />
	<link>http://stocktwitstech.com/warning-signs-flashing-for-adobe/</link>
	<description>Just another StockTwits Network weblog</description>
	<lastBuildDate>Wed, 21 Jul 2010 12:40:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Numbers, Volume 42</title>
		<link>http://stocktwitstech.com/warning-signs-flashing-for-adobe/comment-page-1/#comment-32</link>
		<dc:creator>Numbers, Volume 42</dc:creator>
		<pubDate>Tue, 09 Mar 2010 02:10:28 +0000</pubDate>
		<guid isPermaLink="false">http://stocktwitstech.com/?p=162#comment-32</guid>
		<description>[...] Tempest in a 5% teapot I pointed Leigh at this post by Jeremy Allaire, founder and CEO of BrightCove, which gets into detail on the emerging battle between Flash and HTML5. As the post states, ‘there’s a lot of nuance here’ – and it’s by no means a foregone conclusion that Flash will be going away anytime soon. Also interestingly (and probably not coincidentally), $TIVO announced wide-ranging support for Flash this week.   In addition, Flash currently represents only about 5% of Adobe’s revenue and is dwarfed by the revenues derived from its desktop applications business. [...]</description>
		<content:encoded><![CDATA[<p>[...] Tempest in a 5% teapot I pointed Leigh at this post by Jeremy Allaire, founder and CEO of BrightCove, which gets into detail on the emerging battle between Flash and HTML5. As the post states, ‘there’s a lot of nuance here’ – and it’s by no means a foregone conclusion that Flash will be going away anytime soon. Also interestingly (and probably not coincidentally), $TIVO announced wide-ranging support for Flash this week.   In addition, Flash currently represents only about 5% of Adobe’s revenue and is dwarfed by the revenues derived from its desktop applications business. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coté&#39;s People Over Process &#187; Numbers, Volume 42</title>
		<link>http://stocktwitstech.com/warning-signs-flashing-for-adobe/comment-page-1/#comment-31</link>
		<dc:creator>Coté&#39;s People Over Process &#187; Numbers, Volume 42</dc:creator>
		<pubDate>Mon, 08 Mar 2010 23:41:52 +0000</pubDate>
		<guid isPermaLink="false">http://stocktwitstech.com/?p=162#comment-31</guid>
		<description>[...] Tempest in a 5% teapot  I pointed Leigh at this post by Jeremy Allaire, founder and CEO of BrightCove, which gets into detail on the emerging battle between Flash and HTML5. As the post states, ‘there’s a lot of nuance here’ – and it’s by no means a foregone conclusion that Flash will be going away anytime soon. Also interestingly (and probably not coincidentally), $TIVO announced wide-ranging support for Flash this week.&#160;&#160; In addition, Flash currently represents only about 5% of Adobe’s revenue and is dwarfed by the revenues derived from its desktop applications business. [...]</description>
		<content:encoded><![CDATA[<p>[...] Tempest in a 5% teapot  I pointed Leigh at this post by Jeremy Allaire, founder and CEO of BrightCove, which gets into detail on the emerging battle between Flash and HTML5. As the post states, ‘there’s a lot of nuance here’ – and it’s by no means a foregone conclusion that Flash will be going away anytime soon. Also interestingly (and probably not coincidentally), $TIVO announced wide-ranging support for Flash this week.&nbsp;&nbsp; In addition, Flash currently represents only about 5% of Adobe’s revenue and is dwarfed by the revenues derived from its desktop applications business. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
