MooTools is programming, like a more improved flavor of JS. Since JS is such a different language from most, people don’t really want to deal with it anyway (so the easiest route is always selected).

MooTools is comprehensive, and has a much steeper learning curve. Unless you were already programming, jQuery is MUCH more user-friendly.

Tru dat with addOnLoad working with required modules. MooTools has a bundled package that can create different Moo builds depending on what is needed on a given page.

Also worth noting: addOnLoad (or ready, whichever) have more power inherently than the other libraries do — at least, that I’m aware of. For example, dojo.addOnLoad(obj, “someFunc”) will run obj.someFunc when the DOM is ready, or dojo.addOnLoad(obj, function () {/*…*/}) will run the anonymous function scoped to obj.

I know you could accomplish the latter by doing jQuery.ready(jQuery.proxy(function () {/*…*/}, obj), when using 1.4, and I’m sure other languages have similar (heck, native has bind in some newer browsers which would also do it). Still kind of a neat trick.

Oh, also, addOnLoad, thanks to the require mechanics of Dojo, actually lets you do some sorts of lazy loading. You could chain things, like

dojo.addOnLoad(function () {
// Bind to some button stashed in some node variable
dojo.connect(node, ‘onclick’, function (e) {
// Need something new!
dojo.require(‘some.other.thing’);
dojo.addOnLoad(function () {
// This only runs once the required module has loaded
}); // inner addOnLoad
}); // connect
}); // outer addOnLoad

Which is also to say that technically, addOnLoad isn’t listening just for DOM to be ready, but for all required modules to be loaded, no matter how nested.

A bit off-topic, I suppose, but it does show that things are a bit more powerful here. I suspect jQuery/RequireJS can do similar sorts of things, but I haven’t really dug into that yet.

Yeah
document.addEvent(‘ready’, function(){

})

or

dom.addEvent(‘ready’, function(){

})

would be the only think I would possibly change

“.ready” is too jQuery-ish for me.

That being said, there’s also the native approach for browsers that support it (which is to say, pretty much everything but IE these days, and likely IE9):

​document.addEventListener(‘DOMContentLoaded’, function () {
// Etc
}, false);​​​​​

I love the libraries (particularly enamored with Dojo lately ;)) but it’s good to know how to do it raw too. :D

1.
$(function(){
// $ code here
});

If $ has been released to the global namespace then this also works:

2.
jQuery(function($){
// you can now use $ here
});

@Allen
YUI is the main reason I have delayed the creation of my first vBulletin4/Mootools style (template). Not only its syntax, pardon me, sucks, but it conflicts with other js frameworks. BTW, If I need to use a framework, I shall use only one. The one that is synonymous of FTW!!!

Mootools code has a tendency of looking cleaner in general to me (prototype is similar but it has very wordy method names), which I think is largely due to the fact it takes the approach of prototyping and extending native objects.