<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Speeeeed</title>
	<link>http://blog.circlesixdesign.com/2007/05/29/speeeeed/</link>
	<description>up to the minute updates</description>
	<pubDate>Sat, 22 Nov 2008 13:26:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Marco</title>
		<link>http://blog.circlesixdesign.com/2007/05/29/speeeeed/#comment-10886</link>
		<author>Marco</author>
		<pubDate>Wed, 30 May 2007 07:46:00 +0000</pubDate>
		<guid>http://blog.circlesixdesign.com/2007/05/29/speeeeed/#comment-10886</guid>
		<description>The JS can be compressed on the fly as well with JSLint. My collegue Ed Eliot wrote something nice about that &lt;a href="http://www.ejeliot.com/blog/72" rel="nofollow"&gt;in this article&lt;/a&gt;. I plan to create another WP plugin that combines what Ed describes with what I did to my CSS. The plugin will grab all JS tags, chain them and insert them at the bottom, compressed and cached. Should not be too hard to do I think. It should automate most of the things you described :)

It's harder with JS though and it will probably lead to more problems than CSS because not all Javascript is well written. I guess if you (or a plugin author) write crap code you'll get crap results with it.</description>
		<content:encoded><![CDATA[<p>The JS can be compressed on the fly as well with JSLint. My collegue Ed Eliot wrote something nice about that <a href="http://www.ejeliot.com/blog/72" rel="nofollow">in this article</a>. I plan to create another WP plugin that combines what Ed describes with what I did to my CSS. The plugin will grab all JS tags, chain them and insert them at the bottom, compressed and cached. Should not be too hard to do I think. It should automate most of the things you described :)</p>
<p>It&#8217;s harder with JS though and it will probably lead to more problems than CSS because not all Javascript is well written. I guess if you (or a plugin author) write crap code you&#8217;ll get crap results with&nbsp;it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
