One thing that converted me from Mootools to jQuery was how much control I have over my code with jQuery. With Mootools I found myself constantly constraining m

One thing that converted me from Mootools to jQuery was how much control I have over my code with jQuery. With Mootools I found myself constantly constraining myself to the design patterns the Mootools team found best. Although those design patterns aren't bad, they sometimes don't suit the most intuitive solution to a problem. jQuery on the other hand, lets you do whatever you want. You can use Mootools and jQuery at the same time (which is a killer combination if you use the "Core Builder" for Mootools). Also, the jQuery UI package is fantastic. It is without a doubt a great way to do progressive enhancement: it uses a css framework, sprited icons, and js for the interaction in separate layers. Mootools More feels disjointed and unfocused, while the jQuery UI project feels crisp and professional. Any functionality you like in More is available as jQuery plugins, which brings me to this point: I find it much easier to modify the code for a jQuery plugin than I do a Mootools class. I personally find it much simpler to change a few function calls than redo the structure of a class.