<?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: My Deal with CSS query engines</title>
	<atom:link href="http://comments.deasil.com/2007/02/18/my-deal-with-css-query-engines/feed/" rel="self" type="application/rss+xml" />
	<link>http://comments.deasil.com/2007/02/18/my-deal-with-css-query-engines/</link>
	<description>escape colon w q</description>
	<pubDate>Sat, 22 Nov 2008 09:27:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: John Resig</title>
		<link>http://comments.deasil.com/2007/02/18/my-deal-with-css-query-engines/#comment-29</link>
		<dc:creator>John Resig</dc:creator>
		<pubDate>Mon, 19 Feb 2007 05:14:34 +0000</pubDate>
		<guid isPermaLink="false">http://comments.deasil.com/2007/02/18/my-deal-with-css-query-engines/#comment-29</guid>
		<description>Great point about why CSS Selectors "click". I find that when presenting on jQuery (to designers especially) they get the concepts behind it faster than any other group. This is definitely a case where simplicity far outweighs any speed costs that might arise. (Although, in jQuery 1.1 that's far less of an issue.)</description>
		<content:encoded><![CDATA[<p>Great point about why CSS Selectors &#8220;click&#8221;. I find that when presenting on jQuery (to designers especially) they get the concepts behind it faster than any other group. This is definitely a case where simplicity far outweighs any speed costs that might arise. (Although, in jQuery 1.1 that&#8217;s far less of an issue.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
