Agreed, and I still prefer Moo for my own projects because of how it extends javascript instead of replacing it (like jquery does).
Back when I was learning javascript (2006/2007) it seemed like Mootools was for people who had a good grasp on the language and wanted more from it. I appreciated this, and still think it's better at this than jquery.
I wish Moo had gotten more attention over the years. I get why jquery has done so well, but I don't like its methods.
I still maintain that MooTools was the superior system over jQuery.
jQuery won the war, in the end, because it catered to the 'get it up and running now' crowd over the 'do it right' crowd. It was always easier to understand off the bat, especially if you aren't a trained developer, while MooTools makes for a more long lasting, quality codebase.
No jQuery won the war because it fit with what JavaScript does in the browser while MooTools lost because it was part of the Java/OOP fad of "Well it has a new keyword so let's extend classes with it!" that has (thankfully) been rendered to the dustbin of history where it belongs.
Back when I was learning javascript (2006/2007) it seemed like Mootools was for people who had a good grasp on the language and wanted more from it. I appreciated this, and still think it's better at this than jquery.
I wish Moo had gotten more attention over the years. I get why jquery has done so well, but I don't like its methods.