<?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: YUI Bubbling Library: a seriously cool design pattern</title>
	<atom:link href="http://www.pathf.com/blogs/2007/09/yui-bubbling-li/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2007/09/yui-bubbling-li/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Tue, 02 Dec 2008 00:16:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: francine</title>
		<link>http://www.pathf.com/blogs/2007/09/yui-bubbling-li/#comment-1845</link>
		<dc:creator>francine</dc:creator>
		<pubDate>Mon, 09 Jun 2008 09:18:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=246#comment-1845</guid>
		<description>YUI sucks because i can't get tables to sort :), the documentation is unreadable. Apart from being completely useless it's pretty nice</description>
		<content:encoded><![CDATA[<p>YUI sucks because i can&#8217;t get tables to sort :), the documentation is unreadable. Apart from being completely useless it&#8217;s pretty nice</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MezZzeR</title>
		<link>http://www.pathf.com/blogs/2007/09/yui-bubbling-li/#comment-318</link>
		<dc:creator>MezZzeR</dc:creator>
		<pubDate>Sun, 30 Sep 2007 08:03:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=246#comment-318</guid>
		<description>&lt;p&gt;The Bubbling Library is absolutely awesome. &lt;/p&gt;

&lt;p&gt;Now, everyone that uses Behaviour/EventSelector with Prototype/Scriptaculous can't say, "YUI sucks because you end up writing too much code for each DOM element".&lt;/p&gt;

&lt;p&gt;Kudos to Caridy.&lt;/p&gt;

&lt;p&gt;By the way, event-driven application development like this using css selectors isn't faster. It always has to keep crawling the DOM--but what if you update the DOM dynamically/periodically? You'll need to keep crawling the DOM again and re-attach the listeners. Yes, you write less lines of code--but you end up crawling the DOM too much--which gets CPU intensive (IE6 cries like a baby when crawling, Safari, Firefox, Opera and IE7 can crawl nicely).&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>The Bubbling Library is absolutely awesome. </p>
<p>Now, everyone that uses Behaviour/EventSelector with Prototype/Scriptaculous can&#8217;t say, &#8220;YUI sucks because you end up writing too much code for each DOM element&#8221;.</p>
<p>Kudos to Caridy.</p>
<p>By the way, event-driven application development like this using css selectors isn&#8217;t faster. It always has to keep crawling the DOM&#8211;but what if you update the DOM dynamically/periodically? You&#8217;ll need to keep crawling the DOM again and re-attach the listeners. Yes, you write less lines of code&#8211;but you end up crawling the DOM too much&#8211;which gets CPU intensive (IE6 cries like a baby when crawling, Safari, Firefox, Opera and IE7 can crawl nicely).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
