jQuery has a lot of overhead because of it's event handling, cross- browser normalization, etc, it's a good trade-off for most websites. And you can easily reduce those numbers a lot doing simple optimizations.
On May 21, 11:25 pm, donb <falconwatc...@comcast.net> wrote: > It has apparently sped up 50% with the latest release. > > The time it takes to perform any of those test cases is not important > to me. What is important is the application's perceived speed. I > find jQuery to perform quite satisfactorily in that context. In fact, > the real world involves great expanses of idleness sporadically > interrupted by meaningful work. A few milliseconds here and there > don't really matter 99% of the time. > > Besides, jQuery's greatest strength is the clean and elegant coding > model. I don't think anyone will say speed was the objective of > jQuery - other than speed of learning/designing/coding with the > framework. > > On May 21, 9:57 pm, Alexsandro_xpt <bagul...@gmail.com> wrote: > > > Make this testhttp://dante.dojotoolkit.org/taskspeed/
