Bearfruit

You are right wrt the vibrations in the forums; the Olmo affair was pretty ugly (arrrhg, poor chap; couldn’t he get at least some loyalty from his own team?), and I remember an exemplary forum post where our beloved ‘the moo guy’ explained to a noob in no uncertain terms that he was “not welcome here”, merely because he posted a question in the wrong sub-section.

Cholerics aside, mootools is clean and elegant and very well thought out. I do have some personal issues with it, though, for instance, it seems very DOM element centric (especially with the new DOM storage), thus we had to come up with a different solutuion to the same problem. However, the Moo way is certainly valid.

We have solved the UI library problem by writing our own comprehensive UI on top of Mootools, so we are going to stick with it for some time to come.

The release cycle is too slow. We are waiting for 1.2 since like, forever, and have even implemented a lot of stuff that is promised for the new version on our own, since we want to work with stable versions. It does not help that the blog is updated only every other month or so, and it is hard to get a sense of progress even when monitoring the Trac.

The most serious problem for me is the lack of tools, though. We are using Aptana, and NaturalDocs is not parsed for code completion. Also, Mootools’ class system does not go well with the outline view.
If the moo people could get one of their ranks to write tools, then this would be a major reason to stay on board.