<?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: Why I YUI</title>
	<atom:link href="http://terrychay.com/blog/article/why-yui.shtml/feed" rel="self" type="application/rss+xml" />
	<link>http://terrychay.com/blog/article/why-yui.shtml</link>
	<description>You tell that other boy, not to touch the woodwork...</description>
	<pubDate>Fri, 21 Nov 2008 19:41:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-hemorrhage</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul Reinheimer</title>
		<link>http://terrychay.com/blog/article/why-yui.shtml#comment-372220</link>
		<dc:creator>Paul Reinheimer</dc:creator>
		<pubDate>Tue, 26 Feb 2008 21:32:09 +0000</pubDate>
		<guid isPermaLink="false">http://terrychay.com/blog/?p=679#comment-372220</guid>
		<description>Here at php&#124;architect we run an Ajax course and I also had to make a decision about which framework I would base the class on, I also chose YUI. The key reasons I chose YUI over the options were: documentation, continued support, and excellent documentation. I've experimented with a fair number of different javascript libraries and YUI's documentation seems to be the best out there, well produced, written with lots of examples and notes. I can feel comfortable teaching people how to use something under such active development knowing that the docs will be up to date, ready to help them upgrade down the line.

When I first played with prototype I could figure out how to do things, but the docs were weak, and seemed to be trending behind development. I've seen the same thing in a bunch of other libraries, which is a bit sad :(.</description>
		<content:encoded><![CDATA[<p>Here at php|architect we run an Ajax course and I also had to make a decision about which framework I would base the class on, I also chose YUI. The key reasons I chose YUI over the options were: documentation, continued support, and excellent documentation. I&#8217;ve experimented with a fair number of different javascript libraries and YUI&#8217;s documentation seems to be the best out there, well produced, written with lots of examples and notes. I can feel comfortable teaching people how to use something under such active development knowing that the docs will be up to date, ready to help them upgrade down the line.</p>
<p>When I first played with prototype I could figure out how to do things, but the docs were weak, and seemed to be trending behind development. I&#8217;ve seen the same thing in a bunch of other libraries, which is a bit sad :(.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Mager</title>
		<link>http://terrychay.com/blog/article/why-yui.shtml#comment-371473</link>
		<dc:creator>Andrew Mager</dc:creator>
		<pubDate>Mon, 25 Feb 2008 16:06:39 +0000</pubDate>
		<guid isPermaLink="false">http://terrychay.com/blog/?p=679#comment-371473</guid>
		<description>We use YUI here at CNET now. I need to digg deeper into it. Nice diagram.</description>
		<content:encoded><![CDATA[<p>We use YUI here at CNET now. I need to digg deeper into it. Nice diagram.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
