On Oct 22, 9:58 am, Simon <[EMAIL PROTECTED]> wrote:
> Hi everyone,
> recently I heard about Peppy (http://jamesdonaghue.com/?p=40), a new
> selector engine that is definetly one of the fastest around (http://
> jamesdonaghue.com/static/peppy/profile/slickspeed/#).
> I was wondering if there was a main reason why prototype is so slow
> compared to it, is it all about extending resulting nodes or is it
> that our engine is a bit obsolete. [....]

Probably both.

> in charge of the rewritting of this module and if not, is there a
> possibility to port some routine of Peppy to Prototype to benefit from
> it?

I think there is - as long as its license permits it. Another
technique that would make sense to incorporate into prototype.js is so-
called "bottom-up" selector matching. It does not require collecting
all elements and so usually performs better. NWMatcher [1] and Bouncer
[2] are good examples of these ideas.

[1] http://github.com/dperini/nwevents/tree/master
[2] http://github.com/samleb/bouncer/tree/master

You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 

Reply via email to