In your opinion what makes jquery or prototype any different? They have the same model of support.
I use to share the same opinion with you. Using mootools as a teaching platform but I have been more cautious for a number of reasons. 1. I make sure the individual has a very solid understanding of css and is aware of different issues across browsers. Proper css and html structure can avoid many problems. 2. I teach simple javascript to learn and explain the DOM. Yes, some of this involves inline, clarity is key to foundation. 3. I work on the fundamental of javascript structures and concepts. I usually end up pushing some people away from mootools because of the advance OO paradigm that is in place. These "developers" never want to hear the word polymorphic. This is ok. While to me mootools code is beautiful and elegant there is a lot of magic in the syntax if you don't understand basic OO concepts, closures and the prototype chain. With that said it seems that almost anyone can implement a well written mootools class. This is the dichotomy that creates the tension, the perception of a-holes. I personally believe that this problem is also being addressed by the mootools team with the plugin system that is in development. This will give the world a wonderful resource for drop in scripts. While mantaining a focus towards the core community. Growing pains. On Wed, Sep 17, 2008 at 11:56 PM, tombmedia <[EMAIL PROTECTED]> wrote: > > No one bashes mootools. It's funny how you all say that. We all love > it. > > I used to suggest to EVERYONE starting out with javascript TO use > mootools. The way it standardizes everything, creates a single library > that works flawlessly across all browsers. Browser compatibly is a > huge hurdle in developing with javascript and with that not a concern > developers are able to spend more time being creative. That's why you > see the wide variety of creative juices with all these libraries. > Browser compatibility and flawless execution (at least in some). It is > very fluent, and is well documented. It also had a good community. > Mootools is/was great for all levels of developers, and I'd rather > novices learn the right way off the bat. > > But, once again, this is not a bash on mootools. This is not asking > for support (unless someone wants to create a company and bill me). > This is not a kick in the teeth to all the wonderful contributors and > programmers. But seriously. I have stated that sometimes people don't > subscribe to this list and surf to the page to find their support. I > still don't see that you guys get that. And telling them to subscribe > or else is a little too draconian. I'm not trying to get people upset, > I'm not trying to get people to provide services. I understand you > have your priorities. But read over the responses you guys make to > people. You are A-Class assholes. Which you can totally do, you don't > ask for money, you don't care about the state of the community. The > code speaks for itself. > > Well it does to a certain point, but I get a LOT more from everyones > attitude. There is nothing in the code to make anyone stop using > mootools. Remember that. No one leaves your community for the code. > You need to think about that people. Why would they leave then? > > It sounds like the success of mootools has gone to peoples heads. I > certainly didn't stop using mootools because the code was faulty. I > left because 12 replies to this thread and still no one has > acknowledged the scenario where you don't subscribe, get lost in the > groups and go to an old blog. Probably 10 more responses telling me to > stop demanding support from mootools. Lynch Mob Mentality. Burn the > Witch! > >
