<?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: SproutCore: From MobileMe to 1.0</title>
	<atom:link href="http://ajaxian.com/archives/sproutcore-from-mobileme-to-10/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/sproutcore-from-mobileme-to-10</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: Jordan</title>
		<link>http://ajaxian.com/archives/sproutcore-from-mobileme-to-10/comment-page-1#comment-268708</link>
		<dc:creator>Jordan</dc:creator>
		<pubDate>Thu, 06 Nov 2008 11:51:05 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=4976#comment-268708</guid>
		<description>&lt;blockquote&gt;In particular we think of Prototype, jQuery, and others as “DOM manipulation libraries”; somewhat like low-level drawing APIs.&lt;/blockquote&gt;
Prototype and jQuery are more like &quot;convenience functions&quot; than a drawing library. If SproutCore wants to live on top of Prototype, then they are going to greatly limit the amount of stuff they can achieve if they&#039;re expecting a drawing API.

&lt;blockquote&gt; SproutCore should live above this layer, allowing you to choose whichever drawing library you like to create custom views.&lt;/blockquote&gt;
I think they&#039;ve overestimated the power of those libraries. If you want to be able to change library providers, you&#039;re going to have to write a proxy layer. And by the time you&#039;ve done that, you already have enough code equal to the weight of those libraries.   You might as well just write your own library as it&#039;s not that hard. The hardest part is just the querySelector engine.</description>
		<content:encoded><![CDATA[<blockquote><p>In particular we think of Prototype, jQuery, and others as “DOM manipulation libraries”; somewhat like low-level drawing APIs.</p></blockquote>
<p>Prototype and jQuery are more like &#8220;convenience functions&#8221; than a drawing library. If SproutCore wants to live on top of Prototype, then they are going to greatly limit the amount of stuff they can achieve if they&#8217;re expecting a drawing API.</p>
<blockquote><p> SproutCore should live above this layer, allowing you to choose whichever drawing library you like to create custom views.</p></blockquote>
<p>I think they&#8217;ve overestimated the power of those libraries. If you want to be able to change library providers, you&#8217;re going to have to write a proxy layer. And by the time you&#8217;ve done that, you already have enough code equal to the weight of those libraries.   You might as well just write your own library as it&#8217;s not that hard. The hardest part is just the querySelector engine.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

