External selectors as engines and how to create your own library
With " Sizzle event", the challenge about libraries will move from the coolest/fastest selector engine into the coolest/fastest way to use it for library purpose. Since Sizzle will be just one of them, thanks to our natural behavior ( read: re-create the wheel ) it is possible that there will be more selector engines around the net. So, why we could not create our own library that does just what we need and nothing else, maintaining a decent size and performing like a jaguar :D ??? Here a truly basic example about how to create your own library, basing it over a generic selector engine or generic library (or just its engine, if you prefer one) // our wonderful library constructor function myQuery(){ // just in case we prefer another name for the constructor // this code is "name proof" var callee = arguments.callee; return this instanceof callee ? this : callee.prototype.init.apply(new callee, arguments) ; }; // add some...