Another time: mootools vs jQuery [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 12 years ago.

I've just finished to translate (in Italian...for Italian developers that are too lazy to learn English :D ) this great article (by Aaron Newton) about the topic the title refers to:

http://jqueryvsmootools.com/

While I was doing it, I had the opportunity to focus and to deeply understand the main goals about these two fantastic javascript frameworks.

Leaving out all the details about how each framework work etc etc, I have to tell that I really prefer Mootools (I love its "verbosity" and its way to extend native JS).

I'm kinda new here in the stackoverflow community, and I noticed how much jQuery "questions cloud" is really bigger than Mootools one. So, I don't know if it's just about the popularity or about the fact that people really prefer jQuery instead of Mootools.

Going to the question, I'd like to ask (and I think it's a very good topic to confront each other), if you are experienced with both of them:

Why do you prefer jQ rather than moo, or why do yo开发者_开发技巧u think jQ is more powerful than moo?

Thanks!