<?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: Quicker DOM Traversing with CSS Selectors</title>
	<atom:link href="http://timkadlec.com/2008/03/quicker-dom-traversing-with-css-selectors/feed/" rel="self" type="application/rss+xml" />
	<link>http://timkadlec.com/2008/03/quicker-dom-traversing-with-css-selectors/</link>
	<description>A Wisconsin based web developer writing about the web.</description>
	<lastBuildDate>Sat, 21 Jan 2012 04:29:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Chris</title>
		<link>http://timkadlec.com/2008/03/quicker-dom-traversing-with-css-selectors/comment-page-1/#comment-58</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 05 Mar 2008 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/1969/12/quicker-dom-traversing-with-css-selectors/#comment-58</guid>
		<description>I should mention that the results Robert Biggs has is not using the API you mentioned.  He is mentioned the Slickspeed test which tests how various libraries do DOM selection.</description>
		<content:encoded><![CDATA[<p>I should mention that the results Robert Biggs has is not using the API you mentioned.  He is mentioned the Slickspeed test which tests how various libraries do DOM selection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Kadlec</title>
		<link>http://timkadlec.com/2008/03/quicker-dom-traversing-with-css-selectors/comment-page-1/#comment-59</link>
		<dc:creator>Tim Kadlec</dc:creator>
		<pubDate>Wed, 05 Mar 2008 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/1969/12/quicker-dom-traversing-with-css-selectors/#comment-59</guid>
		<description>@Chris - Actually, the SlickSpeed test does indeed test for the selector API. It runs the tests using the libraries, but also runs the test using native browser support.</description>
		<content:encoded><![CDATA[<p>@Chris &#8211; Actually, the SlickSpeed test does indeed test for the selector API. It runs the tests using the libraries, but also runs the test using native browser support.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://timkadlec.com/2008/03/quicker-dom-traversing-with-css-selectors/comment-page-1/#comment-60</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 05 Mar 2008 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/1969/12/quicker-dom-traversing-with-css-selectors/#comment-60</guid>
		<description>@Tim: I know.  I realized that right after I added the comment.  Actually, what I remember looking at was the DOMAssistant version of Slickspeed not the one referenced by Robert.</description>
		<content:encoded><![CDATA[<p>@Tim: I know.  I realized that right after I added the comment.  Actually, what I remember looking at was the DOMAssistant version of Slickspeed not the one referenced by Robert.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://timkadlec.com/2008/03/quicker-dom-traversing-with-css-selectors/comment-page-1/#comment-49979</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 05 Mar 2008 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/1969/12/quicker-dom-traversing-with-css-selectors/#comment-49979</guid>
		<description>I should mention that the results Robert Biggs has is not using the API you mentioned.  He is mentioned the Slickspeed test which tests how various libraries do DOM selection.</description>
		<content:encoded><![CDATA[<p>I should mention that the results Robert Biggs has is not using the API you mentioned.  He is mentioned the Slickspeed test which tests how various libraries do DOM selection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Kadlec</title>
		<link>http://timkadlec.com/2008/03/quicker-dom-traversing-with-css-selectors/comment-page-1/#comment-49980</link>
		<dc:creator>Tim Kadlec</dc:creator>
		<pubDate>Wed, 05 Mar 2008 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/1969/12/quicker-dom-traversing-with-css-selectors/#comment-49980</guid>
		<description>@Chris - Actually, the SlickSpeed test does indeed test for the selector API. It runs the tests using the libraries, but also runs the test using native browser support.</description>
		<content:encoded><![CDATA[<p>@Chris &#8211; Actually, the SlickSpeed test does indeed test for the selector API. It runs the tests using the libraries, but also runs the test using native browser support.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://timkadlec.com/2008/03/quicker-dom-traversing-with-css-selectors/comment-page-1/#comment-49981</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 05 Mar 2008 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/1969/12/quicker-dom-traversing-with-css-selectors/#comment-49981</guid>
		<description>@Tim: I know.  I realized that right after I added the comment.  Actually, what I remember looking at was the DOMAssistant version of Slickspeed not the one referenced by Robert.</description>
		<content:encoded><![CDATA[<p>@Tim: I know.  I realized that right after I added the comment.  Actually, what I remember looking at was the DOMAssistant version of Slickspeed not the one referenced by Robert.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

