On Mar 25, 4:38 am, John Resig <[email protected]> wrote: > > The point is, you cant move your mouse fast enough, or type so > > quickly, that your event dispatch system is going to get in the > > way. :-) > > It won't explicitly "get in the way" but it will certainly contribute > to un-needed overhead. Right now we're fighting tooth-and-nail to > squeeze every bit of performance out of the event handling code, with > no room for performance regressions.
I don't know how many events you are dispatching, if hundreds then you may have a point. But I suspect that like most of us, it's just a handful. If you want to optimise here then that's you prerogative. > > Think of the code I published another way, apart from setTimeout/ > > setInterval, how else do you know to get a new execution context in > > JavaScript? > > From that perspective, it is very neat - I absolutely agree. Just not > sold with the current proposal. > Well, I'm not really selling anything. I thought I'd hit on a solution to a difficult problem and thought I'd share it. JavaScripters don't seem to share solutions as much as they used to. -dean --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" 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/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
