Krawczyk, Sizzle doesn't cheat, but John Resig has done some great
stuff there, unfortunately all these tricks dont work in IE < 8.
Mainly he's doing caching, but IE has no event when the dom changed,
so caching doesnt work in ie, neither does the use of the
native .querySelectorAll which really boosts some selectors the newest
browsers.
MooTools' new selector engine will also make use of .querySelector and
probably caching (we need to make sure its worth, since you shouldnt
use the same query multiple times anyway).
jan
On Oct 21, 2008, at 22:03, Oskar Krawczyk wrote:
I understand what you're saying Jan, however you need to see the thing
we're seeing – which is MooTools being on the fourth position in the
selector-speed race. And what we'd really like to see is MT being the
leader.
Personally, I'm really psyched to see the new selector engine in
action.
O.
On Oct 21, 7:58 pm, Jan Kassens <[EMAIL PROTECTED]> wrote:
He cheats. He caches elements, even though he cant cache when the dom
changes, so his results would have to be multiplied (slickspeed fires
each query 4 times, iirc).
Btw. we will have a new Selector engine the next release (most
likely).
-jan
/me doesnt like to compare the libraries by the selectors, all
libraries are fast enough already, so selector speed should not make
you're decision, but rather features and code style
On Oct 21, 2008, at 20:48, Danillo Cesar wrote:
Peppy new selector
http://jamesdonaghue.com/?p=40
http://jamesdonaghue.com/static/peppy/profile/slickspeed/
--
-----------------------------------------
Danillo César de O. Melo
www.sook.com.br
--
my blog:http://blog.kassens.net
--
my blog: http://blog.kassens.net
