John Resig wrote: > The trick is that his library, which only does selectors and basic DOM > additions, comes in at 20kb - the same size as jQuery complete (which > includes Ajax, Effects, etc.) > > I have some speed improvements sitting around that need to be merged > in and tested some more. I'm hoping to get them in for jQuery 1.1.3. > When I last tested, the improvements helped to bring us up to around > the level of DOMQuery. Which, I feel, is a good place to be. > > I'll be sure to post an update once I've tested these changes further.
Am I the onlyone who would be hugely interested in a speed improvement plugin? Since I'm doing development for an intranet application that is used mostly over local networks and fast connections, file size is not too important (js is cached anyway after the first download). What I am overly concerned, however, is execution speed. jQuery offers a gazillion possibilities to do some really awesome UI stuff, usability improvements and graphical effetcs, but for me most of all, really makes it possible to create really automated frameworks that enable users with little to none javascript experience to do all kinds of funky ajax stuff, effects, realtime validations and so on just by applying classes to the code. There are a million plugins I'd like to use too, and most of them work really nice together. When adding lots of automated stuff, especially when trying to make it all really really easy to use through binding to classes and general html structures, it can get pretty heavy. We've had the need to strip out stuff cause of selector slowness on large forms and pages with lots of dynamic fields with lots of event binding and element selection going on. I also think I'm not alone on this. the less-than-20kb size is admirable and especially on the public web it's great. The point just is that where jQuery really shines is fast web application development, and through it's use we can develop ever better apps, often pretty large ones, even faster than before. Often on that realm execution speed, rather than download speed, becomes the most important factor. Anyone for a jQueryTurboCharged -plugin? (go John go! This would be a nice show-off to have on the speed comparisons charts when going head to head with the larger more optimized libraries, aye? ;) ) -- Suni _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
