<?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: The eternal question: jQuery or MooTools?</title>
	<atom:link href="http://mandagreen.com/should-choose-jquery-mootools-js-libraries/feed/" rel="self" type="application/rss+xml" />
	<link>http://mandagreen.com/should-choose-jquery-mootools-js-libraries/</link>
	<description>Refresh your vision</description>
	<lastBuildDate>Mon, 23 Apr 2012 08:51:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Cristi</title>
		<link>http://mandagreen.com/should-choose-jquery-mootools-js-libraries/comment-page-1/#comment-446</link>
		<dc:creator>Cristi</dc:creator>
		<pubDate>Mon, 05 Oct 2009 18:57:36 +0000</pubDate>
		<guid isPermaLink="false">http://mandagreen.com/?p=66#comment-446</guid>
		<description>I didn&#039;t say jQuery&#039;s way of doing it was incorrect. I said Mootools is &quot;correct&quot; (note the quotes btw), which doesn&#039;t make the other one incorrect. What I meant was that Mootools extends getElementById and getElemenentsBySelector using one method for each ($ and $$), while jQuery only uses one (the second one), &quot;suppressing&quot; getElementById (again, note the quotes). 
I know it&#039;s trivial to make it respond to $$, and it&#039;s also trivial to make it behave as Mootools, but out of the box they&#039;re different, right?
And, again, you&#039;re right - jQuery was supposed to handle it like that, which is not what I implied.

I feel you&#039;re a bit upset that I said that because you&#039;re a jQuery fan, but please do read the pseudo-disclaimer - I use both of them, I enjoy writing code using either of them, so this post was not for saying jQuery/Mootools is the best. It was meant as an simple, straight-forward objective comparison between the two most popular js frameworks/libraries.

Cheers!</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t say jQuery&#8217;s way of doing it was incorrect. I said Mootools is &#8220;correct&#8221; (note the quotes btw), which doesn&#8217;t make the other one incorrect. What I meant was that Mootools extends getElementById and getElemenentsBySelector using one method for each ($ and $$), while jQuery only uses one (the second one), &#8220;suppressing&#8221; getElementById (again, note the quotes).<br />
I know it&#8217;s trivial to make it respond to $$, and it&#8217;s also trivial to make it behave as Mootools, but out of the box they&#8217;re different, right?<br />
And, again, you&#8217;re right &#8211; jQuery was supposed to handle it like that, which is not what I implied.</p>
<p>I feel you&#8217;re a bit upset that I said that because you&#8217;re a jQuery fan, but please do read the pseudo-disclaimer &#8211; I use both of them, I enjoy writing code using either of them, so this post was not for saying jQuery/Mootools is the best. It was meant as an simple, straight-forward objective comparison between the two most popular js frameworks/libraries.</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grimen</title>
		<link>http://mandagreen.com/should-choose-jquery-mootools-js-libraries/comment-page-1/#comment-445</link>
		<dc:creator>grimen</dc:creator>
		<pubDate>Mon, 05 Oct 2009 17:14:27 +0000</pubDate>
		<guid isPermaLink="false">http://mandagreen.com/?p=66#comment-445</guid>
		<description>This statement is very odd:

the code is much more simple to understand when using $$(’#id a.class’).each(), instead of the same $(’#id a.class’) method as jQuery does. That’s why jQuery is simple, MooTools is “correct”

* First, who said $$ is &quot;correct&quot;?
* Also it&#039;s trivial to make jQuery respond to $$ instead of $
* jQuery was designed to handle it this way - how can that be &quot;not correct&quot;?</description>
		<content:encoded><![CDATA[<p>This statement is very odd:</p>
<p>the code is much more simple to understand when using $$(’#id a.class’).each(), instead of the same $(’#id a.class’) method as jQuery does. That’s why jQuery is simple, MooTools is “correct”</p>
<p>* First, who said $$ is &#8220;correct&#8221;?<br />
* Also it&#8217;s trivial to make jQuery respond to $$ instead of $<br />
* jQuery was designed to handle it this way &#8211; how can that be &#8220;not correct&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cristi</title>
		<link>http://mandagreen.com/should-choose-jquery-mootools-js-libraries/comment-page-1/#comment-385</link>
		<dc:creator>Cristi</dc:creator>
		<pubDate>Thu, 23 Jul 2009 08:24:28 +0000</pubDate>
		<guid isPermaLink="false">http://mandagreen.com/?p=66#comment-385</guid>
		<description>yes, i know, and i couldn&#039;t say i&#039;m totally happy with it. but, as far as I know, there are some ways of using jQuery or Mootools with Magento, instead of Prototype - if one really wants that :)</description>
		<content:encoded><![CDATA[<p>yes, i know, and i couldn&#8217;t say i&#8217;m totally happy with it. but, as far as I know, there are some ways of using jQuery or Mootools with Magento, instead of Prototype &#8211; if one really wants that <img src='http://mandagreen.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toni Anicic</title>
		<link>http://mandagreen.com/should-choose-jquery-mootools-js-libraries/comment-page-1/#comment-384</link>
		<dc:creator>Toni Anicic</dc:creator>
		<pubDate>Thu, 23 Jul 2009 08:22:13 +0000</pubDate>
		<guid isPermaLink="false">http://mandagreen.com/?p=66#comment-384</guid>
		<description>Nice overview. I personally prefer jQuery but Magento is using prototype -.-</description>
		<content:encoded><![CDATA[<p>Nice overview. I personally prefer jQuery but Magento is using prototype -.-</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale</title>
		<link>http://mandagreen.com/should-choose-jquery-mootools-js-libraries/comment-page-1/#comment-377</link>
		<dc:creator>Dale</dc:creator>
		<pubDate>Thu, 09 Jul 2009 06:57:27 +0000</pubDate>
		<guid isPermaLink="false">http://mandagreen.com/?p=66#comment-377</guid>
		<description>Great summary of the Jscript vs Mootools article. While the long version gives you a very clear understanding of the differences it is too long winded.

This shorter version made it very clear that for the different projects it is unique.

I think the clear defining element is the plug-ins. This is the case with WordPress. WordPress is the best, IMHO, Blog/CMS just because of the community which support it and make the many many plug-ins. Because of this I think most of projects going forward will be JQ.

Dale
Web and eCommerces Developer
http://createmy.com.au</description>
		<content:encoded><![CDATA[<p>Great summary of the Jscript vs Mootools article. While the long version gives you a very clear understanding of the differences it is too long winded.</p>
<p>This shorter version made it very clear that for the different projects it is unique.</p>
<p>I think the clear defining element is the plug-ins. This is the case with WordPress. WordPress is the best, IMHO, Blog/CMS just because of the community which support it and make the many many plug-ins. Because of this I think most of projects going forward will be JQ.</p>
<p>Dale<br />
Web and eCommerces Developer<br />
<a href="http://createmy.com.au" rel="nofollow">http://createmy.com.au</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

