<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: AJAX vs Flash as the standard for rich web application development.</title>
	<link>http://www.killersites.com/blog/2005/ajax-vs-flash/</link>
	<description>Real world talk about web design, programming and the business of web design.</description>
	<pubDate>Thu, 24 Jul 2008 02:39:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: ColoradoStartups.com &#187; Six things I learned at BarCamp today</title>
		<link>http://www.killersites.com/blog/2005/ajax-vs-flash/#comment-7351</link>
		<dc:creator>ColoradoStartups.com &#187; Six things I learned at BarCamp today</dc:creator>
		<pubDate>Sun, 12 Nov 2006 05:45:03 +0000</pubDate>
		<guid>http://www.killersites.com/blog/2005/ajax-vs-flash/#comment-7351</guid>
		<description>[...] 5. &#8220;Flash vs Ajax&#8221; lives. First a quick rant. This was a bit of a sales pitch from Adobe, and was more one way than you would expect at BarCamp. I&#8217;d encourage the presenter (Kevin Hoyt) to make the discussion more interactive in the spirit of BarCamp in the future. Anyhoo, it was still pretty damn interesting. This debate has been raging for a while, but it was good to get an update from one of Adobe&#8217;s own Flash specialists, Kevin Hoyt. Kevin showed a little Ajaxy web demo that grabbed 1,000 rows from a database, which took about 3 seconds to execute. Kevin talked about scaling of Ajax apps and the problem associated with the fact that in the end Javascript is handling the work. He showed the same demo using the Flex Ajax Bridge (presumably with the same back end database, etc.) which executed in about a tenth of a second. Basically, while Flash still uses the browser stack, it doesn&#8217;t have to depend on Javascript to parse and handle the resulting XML. He also showed that with 6,000 rows, the Ajax app really started to break down with browser timeouts, etc. after about 30 to 45 seconds. The Flash demo, of course, returned 20,000 records in about half a second. Cool little demo that makes it pretty clear that Flash is something to consider if scale is an issue for your Ajax app. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 5. &#8220;Flash vs Ajax&#8221; lives. First a quick rant. This was a bit of a sales pitch from Adobe, and was more one way than you would expect at BarCamp. I&#8217;d encourage the presenter (Kevin Hoyt) to make the discussion more interactive in the spirit of BarCamp in the future. Anyhoo, it was still pretty damn interesting. This debate has been raging for a while, but it was good to get an update from one of Adobe&#8217;s own Flash specialists, Kevin Hoyt. Kevin showed a little Ajaxy web demo that grabbed 1,000 rows from a database, which took about 3 seconds to execute. Kevin talked about scaling of Ajax apps and the problem associated with the fact that in the end Javascript is handling the work. He showed the same demo using the Flex Ajax Bridge (presumably with the same back end database, etc.) which executed in about a tenth of a second. Basically, while Flash still uses the browser stack, it doesn&#8217;t have to depend on Javascript to parse and handle the resulting XML. He also showed that with 6,000 rows, the Ajax app really started to break down with browser timeouts, etc. after about 30 to 45 seconds. The Flash demo, of course, returned 20,000 records in about half a second. Cool little demo that makes it pretty clear that Flash is something to consider if scale is an issue for your Ajax app. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olivier de Jong</title>
		<link>http://www.killersites.com/blog/2005/ajax-vs-flash/#comment-1268</link>
		<dc:creator>Olivier de Jong</dc:creator>
		<pubDate>Fri, 12 May 2006 09:52:30 +0000</pubDate>
		<guid>http://www.killersites.com/blog/2005/ajax-vs-flash/#comment-1268</guid>
		<description>overshadow the front-end audience needs. That's why Flash is the tool to create graphically esthetic sites targeted on the front-end audience. Take a look at http://rr.com/flash and I would say: Ajax, eat you heart out..</description>
		<content:encoded><![CDATA[<p>overshadow the front-end audience needs. That&#8217;s why Flash is the tool to create graphically esthetic sites targeted on the front-end audience. Take a look at <a href="http://rr.com/flash" rel="nofollow">http://rr.com/flash</a> and I would say: Ajax, eat you heart out..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Mischook</title>
		<link>http://www.killersites.com/blog/2005/ajax-vs-flash/#comment-65</link>
		<dc:creator>Stefan Mischook</dc:creator>
		<pubDate>Fri, 30 Sep 2005 04:03:22 +0000</pubDate>
		<guid>http://www.killersites.com/blog/2005/ajax-vs-flash/#comment-65</guid>
		<description>Hi David,

What can you tell me about Zorn?

I still have soft-spot for Flash - my brother and I started using it way back when it was called 'Future Splash' - this is before Macromedia picked it up.</description>
		<content:encoded><![CDATA[<p>Hi David,</p>
<p>What can you tell me about Zorn?</p>
<p>I still have soft-spot for Flash - my brother and I started using it way back when it was called &#8216;Future Splash&#8217; - this is before Macromedia picked it up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dmendels</title>
		<link>http://www.killersites.com/blog/2005/ajax-vs-flash/#comment-64</link>
		<dc:creator>dmendels</dc:creator>
		<pubDate>Fri, 30 Sep 2005 03:26:35 +0000</pubDate>
		<guid>http://www.killersites.com/blog/2005/ajax-vs-flash/#comment-64</guid>
		<description>Hi,

I think you will like "Zorn".

Regards,
David
macromedia</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I think you will like &#8220;Zorn&#8221;.</p>
<p>Regards,<br />
David<br />
macromedia</p>
]]></content:encoded>
	</item>
</channel>
</rss>
