<?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"
	>
<channel>
	<title>Comments on: Pure GWT - Converting Scriptaculous to GWT</title>
	<atom:link href="http://www.pathf.com/blogs/2007/06/converting_scri/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2007/06/converting_scri/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Fri, 05 Dec 2008 10:27:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Dmitrijs Zaharovs</title>
		<link>http://www.pathf.com/blogs/2007/06/converting_scri/#comment-434</link>
		<dc:creator>Dmitrijs Zaharovs</dc:creator>
		<pubDate>Thu, 07 Jun 2007 08:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=325#comment-434</guid>
		<description>&lt;p&gt;Nice try! Keep up good work!&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Nice try! Keep up good work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bcs06</title>
		<link>http://www.pathf.com/blogs/2007/06/converting_scri/#comment-433</link>
		<dc:creator>bcs06</dc:creator>
		<pubDate>Tue, 05 Jun 2007 16:22:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=325#comment-433</guid>
		<description>&lt;p&gt;Hey Nice one there, i agree partially logically that once the code gets bigger you need some structure in there, but if you use ajax only for view purposes , i guess that you dont need much structure there... just a thought.&lt;/p&gt;

&lt;p&gt;The libaray i would like to see is JQuery, extJS, mootools.&lt;br /&gt;
How long /easy do you think it is to do? what about using groovy?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hey Nice one there, i agree partially logically that once the code gets bigger you need some structure in there, but if you use ajax only for view purposes , i guess that you dont need much structure there&#8230; just a thought.</p>
<p>The libaray i would like to see is JQuery, extJS, mootools.<br />
How long /easy do you think it is to do? what about using groovy?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douche Bag</title>
		<link>http://www.pathf.com/blogs/2007/06/converting_scri/#comment-432</link>
		<dc:creator>Douche Bag</dc:creator>
		<pubDate>Tue, 05 Jun 2007 13:29:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=325#comment-432</guid>
		<description>&lt;p&gt;You're a Google whore. That's the ONLY reason you're pimping GWT.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You&#8217;re a Google whore. That&#8217;s the ONLY reason you&#8217;re pimping GWT.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Preston L. Bannister</title>
		<link>http://www.pathf.com/blogs/2007/06/converting_scri/#comment-431</link>
		<dc:creator>Preston L. Bannister</dc:creator>
		<pubDate>Mon, 04 Jun 2007 17:09:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=325#comment-431</guid>
		<description>&lt;p&gt;It was impossible to take the rest of the article seriously, after this statement:&lt;/p&gt;

&lt;p&gt;" Javascript is great for small libraries but really starts to break down once you build larger systems. "&lt;/p&gt;

&lt;p&gt;There is nothing about Javascript that is more or less unsuitable for large systems.  Yes, this is an intentional flat statement.&lt;/p&gt;

&lt;p&gt;Of course, you generally do not want to be writing large libraries to download to the browser.  This is just classic client/server design - keep complexity on the server and as much as possible push compute work to the clients.  Nothing to do with Javascript.&lt;br /&gt;
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It was impossible to take the rest of the article seriously, after this statement:</p>
<p>&#8221; Javascript is great for small libraries but really starts to break down once you build larger systems. &#8220;</p>
<p>There is nothing about Javascript that is more or less unsuitable for large systems.  Yes, this is an intentional flat statement.</p>
<p>Of course, you generally do not want to be writing large libraries to download to the browser.  This is just classic client/server design - keep complexity on the server and as much as possible push compute work to the clients.  Nothing to do with Javascript.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sander</title>
		<link>http://www.pathf.com/blogs/2007/06/converting_scri/#comment-430</link>
		<dc:creator>Sander</dc:creator>
		<pubDate>Mon, 04 Jun 2007 11:28:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=325#comment-430</guid>
		<description>&lt;p&gt;Obviously Dojo would be a nice lib to convert :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Obviously Dojo would be a nice lib to convert <img src='http://www.pathf.com/blogs/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
