jQuery vs MooTools, MooTools vs jQuery
Every day on twitter I see posts where people are asking themselves the same question: MooTools or jQuery? This is because I have a saved search for “mootools.” Doing a search for “dojo” or “prototype” would find similar tweets from people considering those frameworks or jQuery. The fact is, jQuery is incredibly popular and it’s own popularity breeds adoption as much as the fact that it’s a good bit of software.
Focusing on the “MooTools or jQuery” question, it’s clear that there isn’t a great resource that helps people decide. Looking at the documentation and examples for the two libraries shows they share a lot of functionality. If you’re just now, in 2009, trying to decide which one of these frameworks you want to dive into first, chances are you’re probably relatively new to JavaScript itself and the prospect of comparing the frameworks by actually reading their source code is perhaps more effort than you want to spend. Were I in such a position, I’d want someone to do that for me; to look at them and tell me why some choose one over the other.
So, today I’m releasing jQuery vs MooTools which aims to do just that. No doubt this will cause a stir in our communities but hopefully it will be a healthy one.
I’m not trying to convince people who love jQuery that they’re wrong and should switch, nor am I trying to illustrate to the MooTools community what they’re missing from jQuery. This site is aimed at people who are trying to make this decision and is meant to be an honest comparison of the two libraries. It’s obvious where my bias lays – I’m a MooTools supporter. But I’ve tried to represent the two libraries fairly and, where my opinion is expressed, I try and call that out and say it’s just that – my opinion.
It’s entirely likely that I’ve misrepresented something about the jQuery core library in this post but I’ve done my best not to. Before publishing this site I consulted numerous other contributors to our community. I’ve shared the comparison with authors of other frameworks, bloggers who don’t endorse any particular framework over another, and even sent it to one of the jQuery team members. As I receive feedback, I’ll update the site to incorporate the perspectives of others that may be helpful for the target audience of the comparison (i.e. people considering the two frameworks).
I encourage you to leave comments on the site itself and not here on clientcide.
read on: jQuery vs MooTools
Follow @clientcide on twitter to get notified of new posts.
To follow me personally on twitter, follow @anutron.
May 18th, 2009 at 5:07 pm
Excellent work! congrats :D
a framework vs a toolkit, cool :D
I (L) moo! =)
May 20th, 2009 at 12:04 am
Hi Aaron.
I can’t contact you via “Contact me” on your site. There is some problem while sending message…
I have some propositions. Contact me please:
skype: mounters
icq: 8405402
or via E-Mail.
thx, Alexand.
May 20th, 2009 at 2:31 am
Very interesting Aaron, thank you for all this info!
May 20th, 2009 at 8:28 am
The most unbiased comparison is a source code hoedown between libraries:
http://ajax.wikispaces.com/functional_comparison
May 20th, 2009 at 6:54 pm
JQuery works great in iphone :D
May 21st, 2009 at 1:42 pm
Thanks for the post and the JQuery vs Mootols site, it will surely help me understand both frameworks better :)
May 25th, 2009 at 1:24 pm
Great article. I like that you’re trying to make an honest comparison, rather than proselytize Mootools.
One issue that I think you overlooked was that JS frameworks are seldom used in a vacuum. I think jQuery’s community has done a lot more to ease integration of jQuery with frameworks like rails. (Obviously, Prototype/Scriptaculous are great in this regard as well.)
I see many projects using Rails with jQuery, but I haven’t seen much of mootools/rails integration. There’s a mootools on rails project, but it’s not actively maintained:
http://github.com/pointcom/mootools-on-rails/tree/master
I’d love to see something like CodeOfficer’s js-data-helper to allow seamless rails integration with mootools:
http://github.com/CodeOfficer/js-data-helper/tree/master
May 26th, 2009 at 8:59 am
Excellent article: honest, open minded overview and comparison. Thanks a lot.
May 28th, 2009 at 4:20 am
Excellent.
I’ve been using mootools since moo.fx, jquery was fairly dubious back then.
I thought I’d mention the Wikipedia article on mootools.
It warns of;
. “…needs references that appear in reliable third-party publications.”
. “…may contain improper references to self-published sources.”
. “…insufficient context…”
But then again I did always like mootools “all-we-care-about-is-javascript” attitude :)
Cheers!
May 28th, 2009 at 4:23 am
Love the live comment preview, but the anchor builder isn’t loading it’s background/images (FFox3.0.10)
May 28th, 2009 at 8:18 am
@nick, oddly, it was the live comment preview that was breaking the anchor builder (which took me quite a while to figure out!). Thanks. it’s fixed.