<?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: AJAX performance stats, ROI, and business value</title>
	<atom:link href="http://www.webword.com/wp/2006/01/15/ajax-performance-stats-roi-and-business-value/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webword.com/wp/2006/01/15/ajax-performance-stats-roi-and-business-value/</link>
	<description>The usability blog of John S. Rhodes</description>
	<lastBuildDate>Sun, 17 Oct 2010 00:45:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dietrich Kappe</title>
		<link>http://www.webword.com/wp/2006/01/15/ajax-performance-stats-roi-and-business-value/comment-page-1/#comment-12275</link>
		<dc:creator>Dietrich Kappe</dc:creator>
		<pubDate>Thu, 06 Apr 2006 00:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.webword.com/2006/01/15/ajax-performance-stats-roi-and-business-value/#comment-12275</guid>
		<description>Two points:

1. Productivity could actually increase if we move to a component based GUI model as exemplified by the Echo2 framework (open source). Reminds me of the shift from hand coding graphical interfaces to component GUI&#039;s when the Mac came out.

Use of such a framework would promote good practices like keeping the business logic on the server side.

2. While Ajax *can* make web apps more efficient, the temptation to lard in lots of new features will have us investing in more server hardware (see http://blogs.pathf.com/agileajax/2006/04/yahoo_mail_ajax.html).

Are the old troubles of Client/Server just over the horizon?</description>
		<content:encoded><![CDATA[<p>Two points:</p>
<p>1. Productivity could actually increase if we move to a component based GUI model as exemplified by the Echo2 framework (open source). Reminds me of the shift from hand coding graphical interfaces to component GUI&#8217;s when the Mac came out.</p>
<p>Use of such a framework would promote good practices like keeping the business logic on the server side.</p>
<p>2. While Ajax *can* make web apps more efficient, the temptation to lard in lots of new features will have us investing in more server hardware (see <a href="http://blogs.pathf.com/agileajax/2006/04/yahoo_mail_ajax.html)" rel="nofollow">http://blogs.pathf.com/agileajax/2006/04/yahoo_mail_ajax.html)</a>.</p>
<p>Are the old troubles of Client/Server just over the horizon?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Rhodes</title>
		<link>http://www.webword.com/wp/2006/01/15/ajax-performance-stats-roi-and-business-value/comment-page-1/#comment-11599</link>
		<dc:creator>John Rhodes</dc:creator>
		<pubDate>Sun, 15 Jan 2006 23:59:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.webword.com/2006/01/15/ajax-performance-stats-roi-and-business-value/#comment-11599</guid>
		<description>Exactly. The benefits of Ajax aren&#039;t free. Completely understood.</description>
		<content:encoded><![CDATA[<p>Exactly. The benefits of Ajax aren&#8217;t free. Completely understood.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper Rønn-Jensen</title>
		<link>http://www.webword.com/wp/2006/01/15/ajax-performance-stats-roi-and-business-value/comment-page-1/#comment-11598</link>
		<dc:creator>Jesper Rønn-Jensen</dc:creator>
		<pubDate>Sun, 15 Jan 2006 21:38:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.webword.com/2006/01/15/ajax-performance-stats-roi-and-business-value/#comment-11598</guid>
		<description>Just to clarify my opinion: I still AJAX is a smart move. There are significant productivity benefits (as documented) when &lt;em&gt;using&lt;/em&gt; an AJAX application. 

My point is that the development costs may be increased because of learning costs and that this extra cost should not be ignored.</description>
		<content:encoded><![CDATA[<p>Just to clarify my opinion: I still AJAX is a smart move. There are significant productivity benefits (as documented) when <em>using</em> an AJAX application. </p>
<p>My point is that the development costs may be increased because of learning costs and that this extra cost should not be ignored.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

