Why not jquery ?

http://ajaxian.com/archives/prototype-151-release-candidate-released

the interesting part is that ext (http://www.yui-ext.com/deploy/ext-1.0-alpha3/docs/) now also supports prototype

I didn´t see this discussion before, seems like there is more people voting for Jquery than mootools.
For once, i really can´t stand the pople over at mootools. Even though you have good reason to ask questions,
they just close the thread or flame at you to look in the docs. Ive been trying mootools from the beginning, but i
just can´t see why i should use it, since Jquery does it better and is just about the same size, PLUS i get support!

I really do think that ModX should settle with one library, not using or "flameing" between two or more libraries...
It makes it hard for developers AND users.

Yes, MODx uses MooTools. What the various addons then use are their own business.

So it is decided that ModX is going to stick with Mootools?
Is this confirmed by ModX officially?

I will neither confirm nor deny anything beyond 096 which will contain Mootools for the manager and for Quickedit.

I just don´t understand, why use a completely new library when there are stable alternatives with excessive support and plugins?

What is better with mootools?
Where is mootools going in the future, that for e.x jquery isnt?

Please explain, so that we can understand what is going on.

Maybe you didn’t understand that when I said, "I will neither confirm nor deny anything beyond 096 which will contain Mootools for the manager and for Quickedit." that I meant it.

And perhaps you could read this thread a bit more in depth and read between the lines. For one thing, though, Mootools integration work is done and now the legacy cruft is exorcised.

Quote from: beryl at Mar 27, 2007, 04:40 PM

I just don´t understand, why use a completely new library when there are stable alternatives with excessive support and plugins?

What is better with mootools?
Where is mootools going in the future, that for e.x jquery isnt?

Please explain, so that we can understand what is going on.

You are not alone in asking these questions. A whole lot of time and energy has gone into rewriting the manager and many scripts to use mootools, but I get the sense that this is a decision that is being reevaluated. After 0.9.6 is finished and released I think there will be more movement on this issue, and 0.9.7 is a completely different animal anyway.

Bingo! 097 is a completely different animal that is still heavily in development. There most likely will not be a requirement for any particular js library, though it may ship by default with Mootools simply because it’s done and we want the new API and parsing system out there in the wild as soon as possible. In fact, the manager themes themselves might just scope which library is used. And templating system for that matter. But there’s still things in limbo there. More on that soon enough.

Nice, thanx for clearing things up (?)
I´l be watching out for 0.9.7 then