I started with Prototype/Script.aculo.us, tried MooTools, and moved to JQuery.
I don't have very technical reasons to support this just personal experience. I was amazed by Prototype, having not used a framewqork before, but found it fiddly and not terribly well documented. MooTools was just really hard to get to work at all, so I chucked it as I couldn't afford the learning curve. I tried JQuery and was amazed at it's simplicity, ease of use, documentation and support. I've never looked back, apart from revisiting old projects, ripping out all the Prototype and replacing it! The plugins I have tried have almost always worked seamlessly, and where tweaks have been needed the coding conventions make it easy to rip them apart. Together with JQueryUI it's just great for my needs. I've gone on to do more and code better, bigger things thanks to JQuery, and been pleasantly surprised. I have an In Context Editing system powered almost entirely by JQuery for front end manipulation, and it has been a pleasure to build. To answer you in the format you requested: 1) Ease of use, transparency, support, documentation, plugins 2) = NULL; So, that's my two cents, JQuery FTW! On May 21, 8:05 pm, kiusau <kiu...@mac.com> wrote: > After a badly needed pause of some length, my need for sophisticated > JavaScript has reemerged. During my departure I have discovered two > other similar JavaScript modules called MooTools and Prototype. With > my reemergence I have also realized that all of these require a > certain amount of commitment that goes beyond what I initially > anticipated. What I would like from you all is a convincing argument > to remain that is based on the following comparison: > > 1) What are the principal advantages of jQuery over Prototype and > MooTools? > 2) What are the principal disadvantages of jQuery when compared with > Protoype and MooTools? > > Roddy
