Comments on: Question: Why did you choose MooTools?

By: Florian Pichler

Florian Pichler — Sun, 11 Apr 2010 23:34:36 +0000

I chose MooTools for helping me writing Javascript.

By: deos

deos — Tue, 23 Feb 2010 17:34:36 +0000

until about a half year ago i didn’t use any js-framework at all. just coded everything in easy plan js (yeah, even with IE-support XD). even made every effect myself i wanted to have, just because it was fun. i always knew there are frameworks but i just didn’t want to use them XD then some day i found a great article about a comparison of the big frameworks (wouldn’t make much sense to link it, since its in German). it compared the features and showed examples. after reading it i just new it has to be MooTools, because MooTools actually extends js itself like it should be from the very beginning (like a correct addEvent for every browser). also the coding-style of MooTools is clear and makes sense (you know what a function/class is capable of by its name) and it doesn’t bring a thousand useless functions like most of the other frameworks do (i’m looking at you, jQuery). and of course, being able to create classes in js was the top of perfectness ^^ i tried it, i fell in love with it, and i’m of course sticking with it, using it everywhere i can and trying to get even more and more out of this fantastic framework

some while ago i took a jQuery-plugin (roundAbout) and made a MooTools port of it. guess what, it works even better then the original jQuery-version XD

By: virtualgadjo

virtualgadjo — Sun, 21 Feb 2010 09:11:17 +0000

having, long ago, stopped writing any js (NS6 vs IE war had killed my js pleasure) and was only coding websites serverside. When, reluctantly, i had to put some js into a new website i went looking for something that would take care of browser compatibility for me. i first started with prototype/scriptaculous but was somehow frustrated by the enormous toolbox feeling… browsing the web i ran into mad4milk who drove me to Mootools website. I instantly loved the syntax, the class writing ability, the ‘inline javascript is evil’ catchphrase in the forums and so many other things it would be too long to tell. i knew i had found what i was looking for, never went back from that incredible library. Now, i write tons of unobstrusive js for tons of website, thanks to mooooo )

By: gonchuki

gonchuki — Thu, 18 Feb 2010 16:02:07 +0000

I started back in the day when there was only Prototype and Moo.Fx was a 2.5kb library. Proto has been always kind of buggy and slow, so I jumped to full Mootools since SVN r83 (with which I coded a couple full sites, albeit the early development status of Mootools).

By: arc

arc — Mon, 08 Feb 2010 10:50:04 +0000

when i started js-development, i had to choose between scriptaculous and moo.fx/moo.ajax. since the latter just was much nicer and easier to get into, i used this, and then continued with mootools as it released. still very pleased with my choice. jquery was never an option. just dont like it.

By: Eneko Alonso

Eneko Alonso — Tue, 02 Feb 2010 16:56:53 +0000

To me it was easy. OOP is very easy with Mootools and their syntax is clear and clean.

By: Ryan Florence

Ryan Florence — Sun, 31 Jan 2010 18:27:27 +0000

@ Dru

Out of interest, before using prototype and all the other libraries, were you well versed with javascript as a language or did you find that you learnt things slightly backward as well?

Totally backwards. Another reason I'm glad I chose mootools is that it inadvertently taught me vanilla javascript--and well formed javascript. My vanilla javascript still looks quite similar to my mootools code. I create some classes with a handful of methods and then construct them on my page (though I usually use mootools even on small projects.)

I think advanced javascript (prototypes, classes, etc.) is easier to figure out if you've already got mootools under your belt.

By: Ethan Gardner

Ethan Gardner — Sun, 31 Jan 2010 16:18:49 +0000

I chose MooTools because I began using Joomla which shipped with MooTools 1.11 (now ships with v1.12). I quickly realized that it was a very powerful framework that made sense to someone with knowledge of JavaScript.

The thing I like the most about MooTools is that the syntax is concise but so abstract that you can't tell what is going on.

By: Luke

Luke — Sun, 31 Jan 2010 14:19:04 +0000

MooTools was chosen for me as the framework we use at my work. I quickly fell in love with it and now use it everywhere for all my complex JavaScript applications.

By: Barryvan

Barryvan — Sun, 31 Jan 2010 12:49:58 +0000

I chose MooTools primarily because it provided the right level of flexibility and power. Frameworks such as YUI just try to do too much (at least for my needs) -- if I need UI components, I prefer to write them myself. At the same time, some of the simpler frameworks don't provide enough. I find that MooTools gives me just enough power to ensure that I can develop stuff quickly.

My first 'real' JavaScript coding was in a "framework" that wasn't: an in-house, cobbled-together system developed by a Java developer who a) didn't understand JavaScript, and b) tended to overengineer solutions. When I was tasked with developing a new product, I looked around at the various frameworks, and was drawn to the simple elegance of MooTools. It also helped that, unlike some other frameworks (looking at you, Dojo), the examples actually worked, and the documentation was clean and well-organised.