Jquery or mootools?
5 comments
MooTools makes more sense to me when you actually compare the two apis. If you're a JavaScript fan, MooTools is truer to the language.
Check out http://jqueryvsmootools.com
Check out http://jqueryvsmootools.com
jQuery is a DOM wrapper. MooTools is a JavaScript "extension." (Note the quotes and please don't crucify me)
What that basically means is that jQuery makes working with the DOM tolerable and MooTools makes working with JavaScript tolerable. I, personally, have issues with the DOM but no issues with JavaScript, so I opt for jQuery.
What that basically means is that jQuery makes working with the DOM tolerable and MooTools makes working with JavaScript tolerable. I, personally, have issues with the DOM but no issues with JavaScript, so I opt for jQuery.
Jquery.
In my experience, much more support, plugins, and it's been battle tested pretty well.
In my experience, much more support, plugins, and it's been battle tested pretty well.
jQuery is clearly the one being adopted the most. (Something like 90%, at least from what I've heard on a podcast). Why mess with success?
The recent standardization of event handler attachments (see `.on`) is a lot saner than it used to be, but I believe it is still not there where it should be. (I don't know that place, otherwise I'd have written my own library.)
However, the jQuery ecosystem is hard to leave because
There are a few other bits like the culture of short commands because of chained functions, but I personally find that a very minor detail.
I also happen to like the author's ongoing experiments with performance improvements.