All 3 frameworks have pros and cons. They have many technical similarities and each come with their own set of problems. If you can avoid using a framework, always do that. But if the pros of using a framework outweigh the cons, I think the decision mostly comes down to popularity.
Choose the framework that will have the most documentation, the biggest user community, will be around the longest, will have the most number of developers familiar with it, and can be seen as gaining in popularity rather than declining. If you look at Google Trends to compare the three: http://www.google.com/trends?q=jquery+javascript%2Cmootools+javascript%2Cprototype+javascript you'll see that MooTools and Prototype are steady or declining, while jQuery has a dominant lead in popularity and is increasing rapidly. Granted, this is only an analysis of searches, but it's a fair picture of relative popularity of the different frameworks. There is always some safety in choosing the "market leader" and if you are going in blind with no desire to do an in-depth analysis of each option, then choosing jQuery would probably be your safest best. IMO, Matt Kruse On May 21, 2: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
