On Wed, Oct 15, 2008 at 12:46, Per Cederberg <[EMAIL PROTECTED]> wrote: > I think I fixed the MochiKit.Selector issue with "div ~ p" in r1429 by > adding a uniqueness filter on the results from > MochiKit.Selector.findChildElements. Unless the number of returned > results is very high it should not degrade performance much. And > naturally, this should also fix the issue for "div p". > > Arnar, could you add a new trunk MochiKit to your speed comparison page?
Done. Yup, the number of nodes is not correct (or at least as correct as th other frameworks). Performance takes a minor hit, mainly because it is so bad to begin with :) > Otherwise, I look forward to replacing the current implementation that > is based on eval usage, poor query parsing and slow set handling. Not > much fun to debug at all, actually... Me too. The current implementation is quite bad and it is my fault for not updating it since the early Prototype port. Sizzle is quite simple, there are no specific "tricks" to make it fast, but the design is nice. cheers, Arnar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~----------~----~----~----~------~----~------~--~---
