jQuery, prototype, and MooTools all provide very good to excellent FAQs and documentation on their respective websites.
Barring that, why not just mock up some simple interface (say, something with an accordion interface, making an AJAX call to a static HTML file to replace some content) and try it on all three to see what you like. If you can't bear that thought, just *choose* one. None of my friends were using jQuery when I started using it (now I've converted all of them), but I read an article saying that it was going to be included in ASP.NET MVC and VS 2010. So, I gave it a shot, liked it, so I continue using it. I have friends that swear by YUI, and that's fine for them. I have a friend that would rather fall on his sword than stop using Scriptaculous. But you don't even have to go that far - jQuery has a compatibility mode, YUI uses it's own namespace, etc, etc. You don't have to choose *one* framework (although, I'd recommend it). On Thu, May 21, 2009 at 3: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
