<?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: A Free JavaScript Speed Boost for Everyone!</title>
	<atom:link href="http://www.sitepoint.com/blogs/2008/09/16/a-free-javascript-speed-boost-for-everyone/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2008/09/16/a-free-javascript-speed-boost-for-everyone/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Sun, 08 Nov 2009 19:29:21 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Henrik Lindqvist</title>
		<link>http://www.sitepoint.com/blogs/2008/09/16/a-free-javascript-speed-boost-for-everyone/comment-page-1/#comment-871707</link>
		<dc:creator>Henrik Lindqvist</dc:creator>
		<pubDate>Sun, 01 Feb 2009 20:52:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2996#comment-871707</guid>
		<description>Howdays many selector implementations exists and Dean Edwards may not be the best choice regarding speed. Check out our implementaion &lt;a href=&quot;http://llamalab.com/js/selector/&quot; rel=&quot;nofollow&quot;&gt;Selector.js&lt;/a&gt;, and &lt;a href=&quot;http://llamalab.com/js/selector/slickspeed/index.php&quot; rel=&quot;nofollow&quot;&gt;Slickspeed&lt;/a&gt; benchmarks.</description>
		<content:encoded><![CDATA[<p>Howdays many selector implementations exists and Dean Edwards may not be the best choice regarding speed. Check out our implementaion <a href="http://llamalab.com/js/selector/" rel="nofollow">Selector.js</a>, and <a href="http://llamalab.com/js/selector/slickspeed/index.php" rel="nofollow">Slickspeed</a> benchmarks.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: MarkAJohnson</title>
		<link>http://www.sitepoint.com/blogs/2008/09/16/a-free-javascript-speed-boost-for-everyone/comment-page-1/#comment-796307</link>
		<dc:creator>MarkAJohnson</dc:creator>
		<pubDate>Wed, 17 Sep 2008 21:04:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2996#comment-796307</guid>
		<description>This is indeed good news. It&#039;s nice to know about Base2, too--I hadn&#039;t seen that feature.

To answer the question above about &quot;when will it be available everywhere&quot;, well, the answer is basically it is *already* available everywhere, but older browsers will have to download a JS implementation of it, whereas the newer ones do it natively. If you can afford the performance hit (of node selection across the entire document tree in JS) in the older browsers, you&#039;re good.


Pity it&#039;s CSS selectors, though, instead of XPath. You could always implement the CSS selectors on top of an XPath processor--good luck going the other way.


Oh, well.
</description>
		<content:encoded><![CDATA[<p>This is indeed good news. It&#8217;s nice to know about Base2, too&#8211;I hadn&#8217;t seen that feature.</p>
<p>To answer the question above about &#8220;when will it be available everywhere&#8221;, well, the answer is basically it is *already* available everywhere, but older browsers will have to download a JS implementation of it, whereas the newer ones do it natively. If you can afford the performance hit (of node selection across the entire document tree in JS) in the older browsers, you&#8217;re good.</p>
<p>Pity it&#8217;s CSS selectors, though, instead of XPath. You could always implement the CSS selectors on top of an XPath processor&#8211;good luck going the other way.</p>
<p>Oh, well.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.sitepoint.com/blogs/2008/09/16/a-free-javascript-speed-boost-for-everyone/comment-page-1/#comment-796052</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 17 Sep 2008 12:04:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2996#comment-796052</guid>
		<description>This is very exciting... I wonder if this will have significant speed advantages over current frameworks with similar selector patterns like jQuery... or perhaps they already use these features when available. Ya, that would make sense.

Either way, CSS selecting in the DOM is very cool.</description>
		<content:encoded><![CDATA[<p>This is very exciting&#8230; I wonder if this will have significant speed advantages over current frameworks with similar selector patterns like jQuery&#8230; or perhaps they already use these features when available. Ya, that would make sense.</p>
<p>Either way, CSS selecting in the DOM is very cool.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: elduderino</title>
		<link>http://www.sitepoint.com/blogs/2008/09/16/a-free-javascript-speed-boost-for-everyone/comment-page-1/#comment-796016</link>
		<dc:creator>elduderino</dc:creator>
		<pubDate>Wed, 17 Sep 2008 11:04:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2996#comment-796016</guid>
		<description>It&#039;s an exciting development in javascript but how long is it going to be until we can start using this and be sure it&#039;s going to be working for everyone??</description>
		<content:encoded><![CDATA[<p>It&#8217;s an exciting development in javascript but how long is it going to be until we can start using this and be sure it&#8217;s going to be working for everyone??</p>]]></content:encoded>
	</item>
	<item>
		<title>By: krdr</title>
		<link>http://www.sitepoint.com/blogs/2008/09/16/a-free-javascript-speed-boost-for-everyone/comment-page-1/#comment-795929</link>
		<dc:creator>krdr</dc:creator>
		<pubDate>Wed, 17 Sep 2008 08:00:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2996#comment-795929</guid>
		<description>Andrew, 
there&#039;s pattern called state machine. Instead of checking: if(document.querySelector)on each function call, all you need is to check once, during initialization:&lt;code&gt;
if(document.querySelector) {
    loadDOMSelectorFunctions();
} else {
    loadOldSelectorFunctions();
}&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>Andrew,<br />
there&#8217;s pattern called state machine. Instead of checking: if(document.querySelector)on each function call, all you need is to check once, during initialization:<code>
if(document.querySelector) {
    loadDOMSelectorFunctions();
} else {
    loadOldSelectorFunctions();
}</code></p>]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Tetlaw</title>
		<link>http://www.sitepoint.com/blogs/2008/09/16/a-free-javascript-speed-boost-for-everyone/comment-page-1/#comment-795665</link>
		<dc:creator>Andrew Tetlaw</dc:creator>
		<pubDate>Tue, 16 Sep 2008 23:06:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2996#comment-795665</guid>
		<description>I mentioned it above but here it is again: Safari 3.1, Firefox 3.1, and IE8. As far as Opera goes, it doesn&#039;t appear to be in 9.6 but according to this post: http://my.opera.com/core/blog/selectors-api it is being worked on.</description>
		<content:encoded><![CDATA[<p>I mentioned it above but here it is again: Safari 3.1, Firefox 3.1, and IE8. As far as Opera goes, it doesn&#8217;t appear to be in 9.6 but according to this post: <a href="http://my.opera.com/core/blog/selectors-api" rel="nofollow">http://my.opera.com/core/blog/selectors-api</a> it is being worked on.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Integralist</title>
		<link>http://www.sitepoint.com/blogs/2008/09/16/a-free-javascript-speed-boost-for-everyone/comment-page-1/#comment-795481</link>
		<dc:creator>Integralist</dc:creator>
		<pubDate>Tue, 16 Sep 2008 15:29:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2996#comment-795481</guid>
		<description>Can you confirm which browsers will support the new W3C Selector API?

I assume: Firefox (version?), Opera (version?), Safari (version?), IE8.

I also assume that IE6/7 are off the list.

Ta,

M.</description>
		<content:encoded><![CDATA[<p>Can you confirm which browsers will support the new W3C Selector API?</p>
<p>I assume: Firefox (version?), Opera (version?), Safari (version?), IE8.</p>
<p>I also assume that IE6/7 are off the list.</p>
<p>Ta,</p>
<p>M.</p>]]></content:encoded>
	</item>
</channel>
</rss>
