Slick vs. Sizzle - Pros and Cons of CSS Selector Engines

Question

When do I want to use Slick and when do I want to use Sizzle? What are the pros and cons of each as a standalone CSS selector mechanism? How easy is it to use Slick with jQuery? Can Sizzle be used with Mootools?

Answer 1

http://davidwalsh.name/mootools-sizzle - using mootools with sizzle.

valerio posted a post about why mootools in particular will never use a 3rd party project like sizzle-lookie here http://ajaxian.com/archives/mootools-and-sizzle

from this position, the need to scale the mootools selector engine should have caused a spot (which is a standalone engine, but with the fact that the mootools team is being developed so that it is easy to repair / patch)

You can easily clean the stain and transfer it to any frame. here is the essence of using slick in mootools 1.2.x - http://gist.github.com/361474

interesting usage reports around, http://davidwalsh.name/elements-shorthand-slick for example, but all early adopters, so before 1.3 doesn’t work, I don’t expect this to get too much attention.

as for performance, almost identical to some of the beta tests that I saw some time ago with a hiss, moving forward a bit on things like document.body. in any case, publish your findings, it will be interesting.

Answer 2

I understand this is an older article, but I recently ran into it, trying to find a way to use Sizzle instead of Slick with MooTools, in particular, as an attempt to improve performance. Ultimately, I could not find anything that existed, but the above Gist led me to write a library that allows you to replace Slick for Sizzle without changing the MooTools API. I share it here as a starting point for anyone who might come across this message with a similar intention. The library can be found on GitHub at https://github.com/mzabriskie/sickle