<?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: WebKit gets native getElementsByClassName</title>
	<atom:link href="http://ajaxian.com/archives/webkit-gets-native-getelementsbyclassname/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/webkit-gets-native-getelementsbyclassname</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: dkubb</title>
		<link>http://ajaxian.com/archives/webkit-gets-native-getelementsbyclassname/comment-page-1#comment-260311</link>
		<dc:creator>dkubb</dc:creator>
		<pubDate>Mon, 31 Dec 2007 07:26:07 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3148#comment-260311</guid>
		<description>@K9: I assume that jQuery would do what most other frameworks do now: parse the selector, hand off what it can to the built-in methods, and then use normal JS logic to winnow down the results.  If there&#039;s a getElementsBySelector method, perhaps less of the logic will need to be done in JS, and more by the built-in methods, which is a win for every framework.

Anytime an abstraction is found that is in such common use, I think its reasonable to consider pushing it down a layer in the stack.</description>
		<content:encoded><![CDATA[<p>@K9: I assume that jQuery would do what most other frameworks do now: parse the selector, hand off what it can to the built-in methods, and then use normal JS logic to winnow down the results.  If there&#8217;s a getElementsBySelector method, perhaps less of the logic will need to be done in JS, and more by the built-in methods, which is a win for every framework.</p>
<p>Anytime an abstraction is found that is in such common use, I think its reasonable to consider pushing it down a layer in the stack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: McLars</title>
		<link>http://ajaxian.com/archives/webkit-gets-native-getelementsbyclassname/comment-page-1#comment-260289</link>
		<dc:creator>McLars</dc:creator>
		<pubDate>Wed, 26 Dec 2007 21:45:21 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3148#comment-260289</guid>
		<description>Wow! So now another 0.001% of the browsers will have native functionality that has already been surpassed by all the frameworks. I guess we can just junk those frameworks now. Oh, but it&#039;s faster. I&#039;ll keep that in mind the next time I need to run 10,000 iterations in the real world.</description>
		<content:encoded><![CDATA[<p>Wow! So now another 0.001% of the browsers will have native functionality that has already been surpassed by all the frameworks. I guess we can just junk those frameworks now. Oh, but it&#8217;s faster. I&#8217;ll keep that in mind the next time I need to run 10,000 iterations in the real world.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: K9</title>
		<link>http://ajaxian.com/archives/webkit-gets-native-getelementsbyclassname/comment-page-1#comment-260287</link>
		<dc:creator>K9</dc:creator>
		<pubDate>Wed, 26 Dec 2007 15:11:38 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3148#comment-260287</guid>
		<description>@dkubb - You&#039;re right that CSS/XPath selectors for the DOM are a key abstraction in many libraries. I tend to write fairly complex selectors in jQuery, though, ones which make use of some unique features of that library. 

So assuming that native browser support would lag behind the syntax which, for example, jQuery allows, it makes me wonder whether I would switch to a native implementation if one existed?

Maybe browsers should just support more low-level DOM methods (a la getElementsByClassName) and allow frameworks to tie them together into selector implementations?</description>
		<content:encoded><![CDATA[<p>@dkubb &#8211; You&#8217;re right that CSS/XPath selectors for the DOM are a key abstraction in many libraries. I tend to write fairly complex selectors in jQuery, though, ones which make use of some unique features of that library. </p>
<p>So assuming that native browser support would lag behind the syntax which, for example, jQuery allows, it makes me wonder whether I would switch to a native implementation if one existed?</p>
<p>Maybe browsers should just support more low-level DOM methods (a la getElementsByClassName) and allow frameworks to tie them together into selector implementations?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jmoss</title>
		<link>http://ajaxian.com/archives/webkit-gets-native-getelementsbyclassname/comment-page-1#comment-260274</link>
		<dc:creator>jmoss</dc:creator>
		<pubDate>Mon, 24 Dec 2007 18:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3148#comment-260274</guid>
		<description>It&#039;s definitely gone to plaid.

Now we just gotta wait for IE to catch on.  Ha.</description>
		<content:encoded><![CDATA[<p>It&#8217;s definitely gone to plaid.</p>
<p>Now we just gotta wait for IE to catch on.  Ha.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dkubb</title>
		<link>http://ajaxian.com/archives/webkit-gets-native-getelementsbyclassname/comment-page-1#comment-260273</link>
		<dc:creator>dkubb</dc:creator>
		<pubDate>Mon, 24 Dec 2007 18:49:15 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3148#comment-260273</guid>
		<description>While I think this is fantastic news, I also believe its about time browsers consider adding a native getElementsBySelector method.  If you look at most of the popular libraries they allow you to use CSS or XPath selectors to match elements in the DOM.  When something becomes such a common abstraction, it makes sense that browsers natively support it..</description>
		<content:encoded><![CDATA[<p>While I think this is fantastic news, I also believe its about time browsers consider adding a native getElementsBySelector method.  If you look at most of the popular libraries they allow you to use CSS or XPath selectors to match elements in the DOM.  When something becomes such a common abstraction, it makes sense that browsers natively support it..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor</title>
		<link>http://ajaxian.com/archives/webkit-gets-native-getelementsbyclassname/comment-page-1#comment-260269</link>
		<dc:creator>Trevor</dc:creator>
		<pubDate>Mon, 24 Dec 2007 16:35:02 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3148#comment-260269</guid>
		<description>&quot;Blindingly fast&quot;

When we&#039;re using hyperbole about technology, I think we should just start saying stuff like &quot;so fast it makes you compulsively masturbate.</description>
		<content:encoded><![CDATA[<p>&#8220;Blindingly fast&#8221;</p>
<p>When we&#8217;re using hyperbole about technology, I think we should just start saying stuff like &#8220;so fast it makes you compulsively masturbate.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

