<?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: Serving JavaScript Fast</title>
	<atom:link href="http://ajaxian.com/archives/serving-javascript-fast/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/serving-javascript-fast</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Sat, 20 Mar 2010 06:51:04 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Serving JavaScript Fast</title>
		<link>http://ajaxian.com/archives/serving-javascript-fast/comment-page-1#comment-20203</link>
		<dc:creator>Serving JavaScript Fast</dc:creator>
		<pubDate>Tue, 06 Jun 2006 02:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/serving-javascript-fast#comment-20203</guid>
		<description>[...] Serving JavaScript Fast: &quot; Cal Henderson brings us this new (lengthy) article on ThinkVitamin.com, a look at speeding up the one thing that&#039;s really growing large on Web 2.0-type applications - the Javascript running behind the scenes.   With our so-called &#039;Web 2.0&#039; applications and their rich content and interaction, we expect our applications to increasingly make use of CSS and JavaScript. To make sure these applications are nice and snappy to use, we need to optimize the size and nature of content required to render the page, making sure we&#8217;re delivering the optimum experience. In practice, this means a combination of making our content as small and fast to download as possible, while avoiding unnecessarily refetching unmodified resources. [...]</description>
		<content:encoded><![CDATA[<p>[...] Serving JavaScript Fast: &#8221; Cal Henderson brings us this new (lengthy) article on ThinkVitamin.com, a look at speeding up the one thing that&#8217;s really growing large on Web 2.0-type applications &#8211; the Javascript running behind the scenes.   With our so-called &#8216;Web 2.0&#8242; applications and their rich content and interaction, we expect our applications to increasingly make use of CSS and JavaScript. To make sure these applications are nice and snappy to use, we need to optimize the size and nature of content required to render the page, making sure we&rsquo;re delivering the optimum experience. In practice, this means a combination of making our content as small and fast to download as possible, while avoiding unnecessarily refetching unmodified resources. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://ajaxian.com/archives/serving-javascript-fast/comment-page-1#comment-18691</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Fri, 02 Jun 2006 18:08:39 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/serving-javascript-fast#comment-18691</guid>
		<description>Its nice to see an article with content, thank you</description>
		<content:encoded><![CDATA[<p>Its nice to see an article with content, thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quentin Dubois</title>
		<link>http://ajaxian.com/archives/serving-javascript-fast/comment-page-1#comment-18553</link>
		<dc:creator>Quentin Dubois</dc:creator>
		<pubDate>Fri, 02 Jun 2006 07:42:41 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/serving-javascript-fast#comment-18553</guid>
		<description>What about JSMIN  (http://www.crockford.com/javascript/jsmin.html) to who can also help you to shrink your JS files.</description>
		<content:encoded><![CDATA[<p>What about JSMIN  (<a href="http://www.crockford.com/javascript/jsmin.html" rel="nofollow">http://www.crockford.com/javascript/jsmin.html</a>) to who can also help you to shrink your JS files.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
