<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Re: The Open Web is Slow</title>
	<atom:link href="http://natejc.com/blog/2008/04/re-the-open-web-is-slow/feed/" rel="self" type="application/rss+xml" />
	<link>http://natejc.com/blog/2008/04/re-the-open-web-is-slow/</link>
	<description>Flash &#38; AS3 info, source, &#38; experiments</description>
	<lastBuildDate>Fri, 13 Jan 2012 17:18:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Kevin Dangoor</title>
		<link>http://natejc.com/blog/2008/04/re-the-open-web-is-slow/comment-page-1/#comment-26762</link>
		<dc:creator>Kevin Dangoor</dc:creator>
		<pubDate>Fri, 04 Apr 2008 14:50:07 +0000</pubDate>
		<guid isPermaLink="false">http://natejc.com/blog/?p=94#comment-26762</guid>
		<description>@Nate: one thing to keep in mind is that Adobe does not get revenue from Flash Player directly, since it&#039;s free. I do think Adobe has a fair bit to gain by opening the player, but I (as author of the article that started this) am not calling for Adobe to go as far as open sourcing their player. I&#039;m saying that they should release the SWF spec under open terms so that others can make players.

@Tony: Yes, there *could* be multiple SWF player implementations out there. As long as Adobe stays on top of things, though, their implementation would undoubtedly lead the field by a wide margin. And note that, as is typical in open source, Adobe would retain the &quot;Flash&quot; name. You can&#039;t call it Flash unless Adobe says you can. Much like the situation with Java today.

The point is for people to be able to try things out and use their own creativity to push the bounds of what can be done with a SWF.

@Alan: Wouldn&#039;t Firefox being open source make it more susceptible to security attacks?

The more likely scenario is that security flaws will be noticed and patched more quickly.

I think there&#039;s enough open source running in untrusted network environments at this point that one can&#039;t reasonably make the argument that it will be less secure.</description>
		<content:encoded><![CDATA[<p>@Nate: one thing to keep in mind is that Adobe does not get revenue from Flash Player directly, since it&#8217;s free. I do think Adobe has a fair bit to gain by opening the player, but I (as author of the article that started this) am not calling for Adobe to go as far as open sourcing their player. I&#8217;m saying that they should release the SWF spec under open terms so that others can make players.</p>
<p>@Tony: Yes, there *could* be multiple SWF player implementations out there. As long as Adobe stays on top of things, though, their implementation would undoubtedly lead the field by a wide margin. And note that, as is typical in open source, Adobe would retain the &#8220;Flash&#8221; name. You can&#8217;t call it Flash unless Adobe says you can. Much like the situation with Java today.</p>
<p>The point is for people to be able to try things out and use their own creativity to push the bounds of what can be done with a SWF.</p>
<p>@Alan: Wouldn&#8217;t Firefox being open source make it more susceptible to security attacks?</p>
<p>The more likely scenario is that security flaws will be noticed and patched more quickly.</p>
<p>I think there&#8217;s enough open source running in untrusted network environments at this point that one can&#8217;t reasonably make the argument that it will be less secure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://natejc.com/blog/2008/04/re-the-open-web-is-slow/comment-page-1/#comment-26723</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Fri, 04 Apr 2008 01:33:47 +0000</pubDate>
		<guid isPermaLink="false">http://natejc.com/blog/?p=94#comment-26723</guid>
		<description>Wouldn&#039;t open sourcing the flash player make it susceptible to security attacks?</description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;t open sourcing the flash player make it susceptible to security attacks?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Chatellier</title>
		<link>http://natejc.com/blog/2008/04/re-the-open-web-is-slow/comment-page-1/#comment-26714</link>
		<dc:creator>Nate Chatellier</dc:creator>
		<pubDate>Thu, 03 Apr 2008 22:37:31 +0000</pubDate>
		<guid isPermaLink="false">http://natejc.com/blog/?p=94#comment-26714</guid>
		<description>@Tony: Yeah, you could argue the same thing about Qt, but the way the license is setup, you can&#039;t get away with it. You might be able to steal the general algorithms and methodologies and rewrite everything from scratch, but with the fantastic integration of Adobe products, I think that the only people that could really compete with Adobe are already competing. Plus, again, Qt has managed to prevent this through their licensing scheme.</description>
		<content:encoded><![CDATA[<p>@Tony: Yeah, you could argue the same thing about Qt, but the way the license is setup, you can&#8217;t get away with it. You might be able to steal the general algorithms and methodologies and rewrite everything from scratch, but with the fantastic integration of Adobe products, I think that the only people that could really compete with Adobe are already competing. Plus, again, Qt has managed to prevent this through their licensing scheme.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Fendall</title>
		<link>http://natejc.com/blog/2008/04/re-the-open-web-is-slow/comment-page-1/#comment-26713</link>
		<dc:creator>Tony Fendall</dc:creator>
		<pubDate>Thu, 03 Apr 2008 22:33:13 +0000</pubDate>
		<guid isPermaLink="false">http://natejc.com/blog/?p=94#comment-26713</guid>
		<description>I think the main reason for this, is that if the flash player were open source, then someone could make a slightly modified version of the player.

Then suddenly we would have multiple versions of the player, and developers like us would have the same problems as those who have to deal with multiple browsers.

I agree with you that this could be worked around with the right license, but I still think this is the main reason for Adobe&#039;s descision.</description>
		<content:encoded><![CDATA[<p>I think the main reason for this, is that if the flash player were open source, then someone could make a slightly modified version of the player.</p>
<p>Then suddenly we would have multiple versions of the player, and developers like us would have the same problems as those who have to deal with multiple browsers.</p>
<p>I agree with you that this could be worked around with the right license, but I still think this is the main reason for Adobe&#8217;s descision.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

