<?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: Adobe is “sabotaging” HTML5??</title>
	<atom:link href="http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 07:40:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: SkullKid</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-17010</link>
		<dc:creator>SkullKid</dc:creator>
		<pubDate>Tue, 04 May 2010 02:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-17010</guid>
		<description><![CDATA[All that ranting and &quot;enforced&quot; hatred towards flash won&#039;t lead anywhere as flash won&#039;t disappear any time soon, although I truly believe flash is replaceable on the long run by a unified and strong standard as HTML5 is aiming to be.
There&#039;s still time for Adobe to make Flash Player run smooth on Macs and mobiles. The funny thing is that some people are making that fuss too personal, but I ask them, for how long companies where using Adobe products, including Flash? This &quot;flash is trash&quot; thing is just marketing manipulation because Microsoft and Apple couldn&#039;t do anything better themselves. They just want to take over the market share that Flash owns (I don&#039;t blame their reasons, only their methods).
Microsoft is discretely dropping Silverlight on long terms for HTML5 since it&#039;s open standard and does what SL does simpler and better, also it&#039;s a bit of redundancy against what Flash can do, and I ain&#039;t even counting JavaFX on this amazing equation!
People are falling to this cheap talking on purpose.
]]></description>
		<content:encoded><![CDATA[<p>All that ranting and &#8220;enforced&#8221; hatred towards flash won&#8217;t lead anywhere as flash won&#8217;t disappear any time soon, although I truly believe flash is replaceable on the long run by a unified and strong standard as HTML5 is aiming to be.<br />
There&#8217;s still time for Adobe to make Flash Player run smooth on Macs and mobiles. The funny thing is that some people are making that fuss too personal, but I ask them, for how long companies where using Adobe products, including Flash? This &#8220;flash is trash&#8221; thing is just marketing manipulation because Microsoft and Apple couldn&#8217;t do anything better themselves. They just want to take over the market share that Flash owns (I don&#8217;t blame their reasons, only their methods).<br />
Microsoft is discretely dropping Silverlight on long terms for HTML5 since it&#8217;s open standard and does what SL does simpler and better, also it&#8217;s a bit of redundancy against what Flash can do, and I ain&#8217;t even counting JavaFX on this amazing equation!<br />
People are falling to this cheap talking on purpose.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luda</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-17009</link>
		<dc:creator>Luda</dc:creator>
		<pubDate>Fri, 26 Mar 2010 05:55:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-17009</guid>
		<description><![CDATA[No one needs HTML5. We need XHTML 2.
]]></description>
		<content:encoded><![CDATA[<p>No one needs HTML5. We need XHTML 2.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carsten</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-17008</link>
		<dc:creator>Carsten</dc:creator>
		<pubDate>Mon, 22 Feb 2010 14:47:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-17008</guid>
		<description><![CDATA[I really hope Adobe will take a look behind the Adobe-rant and see the Problem with Technologies like Flash on Macs or Mobile Devices in general. They are slow as hell and even a video raises up the CPU usage on my MacPro. WTF?
I would really like to see (and code) Flash/Actionscript &lt;b&gt;on top of HTML5&lt;/b&gt;, but only if the Technology gets a gigant leap forward in case of performance. There is a good reason for Apple&#039;s beginning dislike of Flash beside Mr. Jobbs eccentric behavior...!
]]></description>
		<content:encoded><![CDATA[<p>I really hope Adobe will take a look behind the Adobe-rant and see the Problem with Technologies like Flash on Macs or Mobile Devices in general. They are slow as hell and even a video raises up the CPU usage on my MacPro. WTF?<br />
I would really like to see (and code) Flash/Actionscript <b>on top of HTML5</b>, but only if the Technology gets a gigant leap forward in case of performance. There is a good reason for Apple&#8217;s beginning dislike of Flash beside Mr. Jobbs eccentric behavior&#8230;!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-17007</link>
		<dc:creator>Randy</dc:creator>
		<pubDate>Fri, 19 Feb 2010 00:26:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-17007</guid>
		<description><![CDATA[Lazy, lazy! Wish more companies would be as lazy and give us wonderful programs like Photoshop, Illustrator, Lightroom,etc.
]]></description>
		<content:encoded><![CDATA[<p>Lazy, lazy! Wish more companies would be as lazy and give us wonderful programs like Photoshop, Illustrator, Lightroom,etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-17006</link>
		<dc:creator>Randy</dc:creator>
		<pubDate>Fri, 19 Feb 2010 00:19:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-17006</guid>
		<description><![CDATA[Lazy, lazy! Wish more companies would be as lazy and give us wonderful programs like Photoshop, Illustrator, Lightroom,etc.
]]></description>
		<content:encoded><![CDATA[<p>Lazy, lazy! Wish more companies would be as lazy and give us wonderful programs like Photoshop, Illustrator, Lightroom,etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: curttech</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-17005</link>
		<dc:creator>curttech</dc:creator>
		<pubDate>Thu, 18 Feb 2010 08:44:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-17005</guid>
		<description><![CDATA[&lt;a href=&quot;http://www.w3schools.com/xhtml/xhtml_why.asp&quot; rel=&quot;nofollow&quot;&gt;http://www.w3schools.com/xhtml/xhtml_why.asp&lt;/a&gt;
]]></description>
		<content:encoded><![CDATA[<p><a href="http://www.w3schools.com/xhtml/xhtml_why.asp" rel="nofollow">http://www.w3schools.com/xhtml/xhtml_why.asp</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LazyAdobe</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-17004</link>
		<dc:creator>LazyAdobe</dc:creator>
		<pubDate>Tue, 16 Feb 2010 16:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-17004</guid>
		<description><![CDATA[&lt;a href=&quot;http://blogs.zdnet.com/security/?p=5473&quot; rel=&quot;nofollow&quot;&gt;http://blogs.zdnet.com/security/?p=5473&lt;/a&gt;
&quot;Report: Malicious PDF files comprised 80 percent of all exploits for 2009&quot;
Adobe, biggest security threat to your PC with Flash and PDF. Lazy company is LAZY.
]]></description>
		<content:encoded><![CDATA[<p><a href="http://blogs.zdnet.com/security/?p=5473" rel="nofollow">http://blogs.zdnet.com/security/?p=5473</a><br />
&#8220;Report: Malicious PDF files comprised 80 percent of all exploits for 2009&#8243;<br />
Adobe, biggest security threat to your PC with Flash and PDF. Lazy company is LAZY.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morgan</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-17003</link>
		<dc:creator>Morgan</dc:creator>
		<pubDate>Tue, 16 Feb 2010 12:27:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-17003</guid>
		<description><![CDATA[Okay; I&#039;ve read what I can find of the relevant posts on the public-html mailing list (the entire &#039;Publish * as FPWDs&#039; and &#039;clarification on Adobe blocking&#039; threads) and IMO, there&#039;s more than a grain of truth there.
Sure, you can make the argument that they&#039;re not blocking HTML5, but they ARE trying to block (via delay) Canvas as a separate specification.  Requesting that a spec not be published until a not-yet-written spec can be published in its place is how you block progress in a specification process.  It&#039;s a passive aggressive approach, which is common in spec politics.
If I&#039;m reading the list right, they ARE explicitly opposing publication of the Microdata spec, which makes me a bit angry.  RDFa requires XML to implement, whereas Microdata can be implemented in HTML directly without having to build an XML version of a document.  This makes Microdata substantially better than RDFa for normal web use, and suggesting that the two standards are equivalent is at worst a lie and at best fundamentally ignoring  ease of use for web developers.
Now, to be specific, I&#039;m not arguing bad faith on Adobe&#039;s part as a company.  I&#039;m arguing passive-aggressive axe-grinding on the part of the specific members (for Microdata) and maybe a LITTLE bad faith on that person&#039;s part regarding Canvas2D.
Specifically arguing that Microdata should not be put forward as a working draft is a move that is designed to push the use of XML as an underlying format for web browsing, which has been shown pretty clearly (to rank and file web developers, as opposed to tool makers who spooge over the idea) to be a bad direction.  That&#039;s clear axe grinding, imo.
Arguing that the Canvas 2D specification should be set aside until a competing proposal can be published is problematic.  It would create a public perception that canvas is being set aside for an indeterminate amount of time, which would limit adoption, which would definitely benefit Adobe.  That...smells at least a little like bad faith.  Not having access to the private mailing lists, I don&#039;t know if there were extensive objections not listed here, but the two that I&#039;ve seen make me uncomfortable about the individuals working on the W3C side of the specification.
That said, I strongly support the WHAT-WG as an entirely separate entity from the W3C.  The W3C has demonstrated clearly that it can&#039;t get $#!t done.  Thankfully it appears most browser developers are building to the WHAT-WG spec, and are not waiting for the W3C to go through its motions.
]]></description>
		<content:encoded><![CDATA[<p>Okay; I&#8217;ve read what I can find of the relevant posts on the public-html mailing list (the entire &#8216;Publish * as FPWDs&#8217; and &#8216;clarification on Adobe blocking&#8217; threads) and IMO, there&#8217;s more than a grain of truth there.<br />
Sure, you can make the argument that they&#8217;re not blocking HTML5, but they ARE trying to block (via delay) Canvas as a separate specification.  Requesting that a spec not be published until a not-yet-written spec can be published in its place is how you block progress in a specification process.  It&#8217;s a passive aggressive approach, which is common in spec politics.<br />
If I&#8217;m reading the list right, they ARE explicitly opposing publication of the Microdata spec, which makes me a bit angry.  RDFa requires XML to implement, whereas Microdata can be implemented in HTML directly without having to build an XML version of a document.  This makes Microdata substantially better than RDFa for normal web use, and suggesting that the two standards are equivalent is at worst a lie and at best fundamentally ignoring  ease of use for web developers.<br />
Now, to be specific, I&#8217;m not arguing bad faith on Adobe&#8217;s part as a company.  I&#8217;m arguing passive-aggressive axe-grinding on the part of the specific members (for Microdata) and maybe a LITTLE bad faith on that person&#8217;s part regarding Canvas2D.<br />
Specifically arguing that Microdata should not be put forward as a working draft is a move that is designed to push the use of XML as an underlying format for web browsing, which has been shown pretty clearly (to rank and file web developers, as opposed to tool makers who spooge over the idea) to be a bad direction.  That&#8217;s clear axe grinding, imo.<br />
Arguing that the Canvas 2D specification should be set aside until a competing proposal can be published is problematic.  It would create a public perception that canvas is being set aside for an indeterminate amount of time, which would limit adoption, which would definitely benefit Adobe.  That&#8230;smells at least a little like bad faith.  Not having access to the private mailing lists, I don&#8217;t know if there were extensive objections not listed here, but the two that I&#8217;ve seen make me uncomfortable about the individuals working on the W3C side of the specification.<br />
That said, I strongly support the WHAT-WG as an entirely separate entity from the W3C.  The W3C has demonstrated clearly that it can&#8217;t get $#!t done.  Thankfully it appears most browser developers are building to the WHAT-WG spec, and are not waiting for the W3C to go through its motions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-17002</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 16 Feb 2010 11:40:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-17002</guid>
		<description><![CDATA[No, no, no.  No proprietary technology belongs as a standard on the web.  Period.  This applies to Microsoft&#039;s Silverlight just as much as it does to Adobe&#039;s Flash.  The web, by definition and the content on the web should be available to all, not just to those platforms sanctioned by any one company.  While we all love Adobe&#039;s products for content creation, they need to step back in favor of more open standards like HTML 5.  If elements of Flash are important, then open up the standard and push to have it included in HTML 5 (or 6), etc.
Just take a look at Apple&#039;s situation for example.  Why should Apple be dependent upon Adobe when it comes time to switch to different processors (PowerPC, Intel, Arm, etc.) just to do something as simple as viewing web content?  How about moving to 64bit?  Flash is notoriously slow and buggy on the Mac as compared to the Windows version.  I&#039;m sure Apple is tired of that situation and likewise wants to take over responsibility for that function.  If it means changing the way things are done through sales of popular devices, I say more power to them.  That&#039;s the catalyst needed to make change happen.
]]></description>
		<content:encoded><![CDATA[<p>No, no, no.  No proprietary technology belongs as a standard on the web.  Period.  This applies to Microsoft&#8217;s Silverlight just as much as it does to Adobe&#8217;s Flash.  The web, by definition and the content on the web should be available to all, not just to those platforms sanctioned by any one company.  While we all love Adobe&#8217;s products for content creation, they need to step back in favor of more open standards like HTML 5.  If elements of Flash are important, then open up the standard and push to have it included in HTML 5 (or 6), etc.<br />
Just take a look at Apple&#8217;s situation for example.  Why should Apple be dependent upon Adobe when it comes time to switch to different processors (PowerPC, Intel, Arm, etc.) just to do something as simple as viewing web content?  How about moving to 64bit?  Flash is notoriously slow and buggy on the Mac as compared to the Windows version.  I&#8217;m sure Apple is tired of that situation and likewise wants to take over responsibility for that function.  If it means changing the way things are done through sales of popular devices, I say more power to them.  That&#8217;s the catalyst needed to make change happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-17001</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 16 Feb 2010 11:39:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-17001</guid>
		<description><![CDATA[No, no, no.  No proprietary technology belongs as a standard on the web.  Period.  This applies to Microsoft&#039;s Silverlight just as much as it does to Adobe&#039;s Flash.  The web, by definition and the content on the web should be available to all, not just to those platforms sanctioned by any one company.  While we all love Adobe&#039;s products for content creation, they need to step back in favor of more open standards like HTML 5.  If elements of Flash are important, then open up the standard and push to have it included in HTML 5 (or 6), etc.
Just take a look at Apple&#039;s situation for example.  Why should Apple be dependent upon Adobe when it comes time to switch to different processors (PowerPC, Intel, Arm, etc.) just to do something as simple as viewing web content?  How about moving to 64bit?  Flash is notoriously slow and buggy on the Mac as compared to the Windows version.  I&#039;m sure Apple is tired of that situation and likewise wants to take over responsibility for that function.  If it means changing the way things are done through sales of popular devices, I say more power to them.  That&#039;s the catalyst needed to make change happen.
]]></description>
		<content:encoded><![CDATA[<p>No, no, no.  No proprietary technology belongs as a standard on the web.  Period.  This applies to Microsoft&#8217;s Silverlight just as much as it does to Adobe&#8217;s Flash.  The web, by definition and the content on the web should be available to all, not just to those platforms sanctioned by any one company.  While we all love Adobe&#8217;s products for content creation, they need to step back in favor of more open standards like HTML 5.  If elements of Flash are important, then open up the standard and push to have it included in HTML 5 (or 6), etc.<br />
Just take a look at Apple&#8217;s situation for example.  Why should Apple be dependent upon Adobe when it comes time to switch to different processors (PowerPC, Intel, Arm, etc.) just to do something as simple as viewing web content?  How about moving to 64bit?  Flash is notoriously slow and buggy on the Mac as compared to the Windows version.  I&#8217;m sure Apple is tired of that situation and likewise wants to take over responsibility for that function.  If it means changing the way things are done through sales of popular devices, I say more power to them.  That&#8217;s the catalyst needed to make change happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-17000</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 16 Feb 2010 11:38:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-17000</guid>
		<description><![CDATA[No, no, no.  No proprietary technology belongs as a standard on the web.  Period.  This applies to Microsoft&#039;s Silverlight just as much as it does to Adobe&#039;s Flash.  The web, by definition and the content on the web should be available to all, not just to those platforms sanctioned by any one company.  While we all love Adobe&#039;s products for content creation, they need to step back in favor of more open standards like HTML 5.  If elements of Flash are important, then open up the standard and push to have it included in HTML 5 (or 6), etc.
Just take a look at Apple&#039;s situation for example.  Why should Apple be dependent upon Adobe when it comes time to switch to different processors (PowerPC, Intel, Arm, etc.) just to do something as simple as viewing web content?  How about moving to 64bit?  Flash is notoriously slow and buggy on the Mac as compared to the Windows version.  I&#039;m sure Apple is tired of that situation and likewise wants to take over responsibility for that function.  If it means changing the way things are done through sales of popular devices, I say more power to them.  That&#039;s the catalyst needed to make change happen.
]]></description>
		<content:encoded><![CDATA[<p>No, no, no.  No proprietary technology belongs as a standard on the web.  Period.  This applies to Microsoft&#8217;s Silverlight just as much as it does to Adobe&#8217;s Flash.  The web, by definition and the content on the web should be available to all, not just to those platforms sanctioned by any one company.  While we all love Adobe&#8217;s products for content creation, they need to step back in favor of more open standards like HTML 5.  If elements of Flash are important, then open up the standard and push to have it included in HTML 5 (or 6), etc.<br />
Just take a look at Apple&#8217;s situation for example.  Why should Apple be dependent upon Adobe when it comes time to switch to different processors (PowerPC, Intel, Arm, etc.) just to do something as simple as viewing web content?  How about moving to 64bit?  Flash is notoriously slow and buggy on the Mac as compared to the Windows version.  I&#8217;m sure Apple is tired of that situation and likewise wants to take over responsibility for that function.  If it means changing the way things are done through sales of popular devices, I say more power to them.  That&#8217;s the catalyst needed to make change happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-16999</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 16 Feb 2010 11:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-16999</guid>
		<description><![CDATA[No, no, no.  No proprietary technology belongs as a standard on the web.  Period.  This applies to Microsoft&#039;s Silverlight just as much as it does to Adobe&#039;s Flash.  The web, by definition and the content on the web should be available to all, not just to those platforms sanctioned by any one company.  While we all love Adobe&#039;s products for content creation, they need to step back in favor of more open standards like HTML 5.  If elements of Flash are important, then open up the standard and push to have it included in HTML 5 (or 6), etc.
Just take a look at Apple&#039;s situation for example.  Why should Apple be dependent upon Adobe when it comes time to switch to different processors (PowerPC, Intel, Arm, etc.) just to do something as simple as viewing web content?  How about moving to 64bit?  Flash is notoriously slow and buggy on the Mac as compared to the Windows version.  I&#039;m sure Apple is tired of that situation and likewise wants to take over responsibility for that function.  If it means changing the way things are done through sales of popular devices, I say more power to them.  That&#039;s the catalyst needed to make change happen.
]]></description>
		<content:encoded><![CDATA[<p>No, no, no.  No proprietary technology belongs as a standard on the web.  Period.  This applies to Microsoft&#8217;s Silverlight just as much as it does to Adobe&#8217;s Flash.  The web, by definition and the content on the web should be available to all, not just to those platforms sanctioned by any one company.  While we all love Adobe&#8217;s products for content creation, they need to step back in favor of more open standards like HTML 5.  If elements of Flash are important, then open up the standard and push to have it included in HTML 5 (or 6), etc.<br />
Just take a look at Apple&#8217;s situation for example.  Why should Apple be dependent upon Adobe when it comes time to switch to different processors (PowerPC, Intel, Arm, etc.) just to do something as simple as viewing web content?  How about moving to 64bit?  Flash is notoriously slow and buggy on the Mac as compared to the Windows version.  I&#8217;m sure Apple is tired of that situation and likewise wants to take over responsibility for that function.  If it means changing the way things are done through sales of popular devices, I say more power to them.  That&#8217;s the catalyst needed to make change happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-16998</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 16 Feb 2010 11:36:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-16998</guid>
		<description><![CDATA[No, no, no.  No proprietary technology belongs as a standard on the web.  Period.  This applies to Microsoft&#039;s Silverlight just as much as it does to Adobe&#039;s Flash.  The web, by definition and the content on the web should be available to all, not just to those platforms sanctioned by any one company.  While we all love Adobe&#039;s products for content creation, they need to step back in favor of more open standards like HTML 5.  If elements of Flash are important, then open up the standard and push to have it included in HTML 5 (or 6), etc.
Just take a look at Apple&#039;s situation for example.  Why should Apple be dependent upon Adobe when it comes time to switch to different processors (PowerPC, Intel, Arm, etc.) just to do something as simple as viewing web content?  How about moving to 64bit?  Flash is notoriously slow and buggy on the Mac as compared to the Windows version.  I&#039;m sure Apple is tired of that situation and likewise wants to take over responsibility for that function.  If it means changing the way things are done through sales of popular devices, I say more power to them.  That&#039;s the catalyst needed to make change happen.
]]></description>
		<content:encoded><![CDATA[<p>No, no, no.  No proprietary technology belongs as a standard on the web.  Period.  This applies to Microsoft&#8217;s Silverlight just as much as it does to Adobe&#8217;s Flash.  The web, by definition and the content on the web should be available to all, not just to those platforms sanctioned by any one company.  While we all love Adobe&#8217;s products for content creation, they need to step back in favor of more open standards like HTML 5.  If elements of Flash are important, then open up the standard and push to have it included in HTML 5 (or 6), etc.<br />
Just take a look at Apple&#8217;s situation for example.  Why should Apple be dependent upon Adobe when it comes time to switch to different processors (PowerPC, Intel, Arm, etc.) just to do something as simple as viewing web content?  How about moving to 64bit?  Flash is notoriously slow and buggy on the Mac as compared to the Windows version.  I&#8217;m sure Apple is tired of that situation and likewise wants to take over responsibility for that function.  If it means changing the way things are done through sales of popular devices, I say more power to them.  That&#8217;s the catalyst needed to make change happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Smith</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-16997</link>
		<dc:creator>David Smith</dc:creator>
		<pubDate>Tue, 16 Feb 2010 09:29:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-16997</guid>
		<description><![CDATA[Ah. &#039;None of the above&#039;, then...
]]></description>
		<content:encoded><![CDATA[<p>Ah. &#8216;None of the above&#8217;, then&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A S BAKER</title>
		<link>http://blogs.adobe.com/jnack/2010/02/adobe_is_sabotaging_html5.html#comment-16996</link>
		<dc:creator>A S BAKER</dc:creator>
		<pubDate>Tue, 16 Feb 2010 09:03:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2010/02/adobe-is-sabotaging-html5.html#comment-16996</guid>
		<description><![CDATA[OK. Now I have no idea what you&#039;re talking about.
]]></description>
		<content:encoded><![CDATA[<p>OK. Now I have no idea what you&#8217;re talking about.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
