I guess the slickspeed was truely useful in the begining and in emerging frameworks... right now most frameworks are already highly optimized and will rely mainly on the javascript engine of the browsers (read V8, MonkeyWhatever..etc) to gain more speed.
In a 1000 elements query, what does 100ms really mean? Will you really really need to select 1000 elements at once? ;-) On Tue, Oct 28, 2008 at 1:40 PM, JamesDonaghue <[EMAIL PROTECTED]> wrote: > > Peppy doesn't cheat, it was a bug (in IE only) and it has been fixed > in the 0.1.2 release: http://jamesdonaghue.com/static/peppy/. > > Also, if selector engines speeds aren't important then why even have a > tool like Slickspeed? > In fact why bother developing a selector engine at all if it is so > rarely used or is so unimportant? > > The selector engines that exist are already fast, however it has been > shown that they can in fact be faster. I don't understand the > argument against this. > The importance of web applications is very great and anywhere that we > can achieve speed gains we should. > > > On Oct 22, 12:27 pm, davidwalsh83 <[EMAIL PROTECTED]> wrote: >> I agree with Bango. Is there really a difference between 2 and 5 >> milliseconds? They're all fast and what should be avoided is a >> "pissing contest." >> >> Great work Tom, Jan, and the rest of the team! -- ◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦ Ivanicus' Code Box http://ivanicus.com/
