Comments on: Nice Framework Comparison (mostly on selector speed)

By: peter

peter — Thu, 22 Jan 2009 22:03:55 +0000

Akismet for Wordpress helps a lot. Since i have it i have less than 5 spams made it into my comments for approval queue.

By: Aaron N.

Aaron N. — Wed, 21 Jan 2009 17:28:37 +0000

@peter, I require people to register to cut down on the spam. For a while there you didn’t have to register, but it was getting out of hand. Even with Wordpress’s new tools I’m reluctant to remove it, but perhaps you are right. I’ll switch it and see if things go crazy.

By: peter

peter — Wed, 21 Jan 2009 15:01:16 +0000

@ samgoody “it must be updated to include Sizzle” – It has. JQuery now use Sizzle and have posted their own tests.

“I see that everyone does lousy on IE8, especially us” – IE8 has some serious problems with javascript which I hope will be a bit cleared until win7 reaches RTM. However Mootools is not that lousy especially compared with Dojo which fails on 11 tests

@Aaron – why don’t you include normal comment form (not needing to register) with approval before appearing on the post (or captcha)

By: samgoody

samgoody — Tue, 20 Jan 2009 22:55:33 +0000

I know your attitude about looking for speed improvements this way. I was more curious why Prototype would not adopt it or Sizzle, but recognize that you are not the address for the answer..

I see that everyone does lousy on IE8, especially us. I assume that will improve as the browser moves out of beta (yeah, right), especially considering as I have heard it will support more native selection. Right? (um, ok. I didn’t say anything.)

By: Aaron N.

Aaron N. — Tue, 20 Jan 2009 16:22:49 +0000

I can’t say I know what the story is with Peppy. I will say that at this point I feel like the selector differences are negligible for real world use. jQuery encourages you to use selectors in your writing often and event to duplicate the same query where it is convenient to your coding. Having your selector engine cache is obviously important in that environment. But the actual selector work is basically as fast as it can get in current browsers (as illustrated by Valerio’s test where he removed the DOM extension from MooTools and compared it to others).

I think most people evaluating frameworks now no longer use selector speed as a criterion for their selection. This post w/ the analysis of the different frameworks only further illustrates it. MooTools and jQuery are neck and neck in the tests for the most part, but I don’t think people are jumping to these frameworks because of it.

By: samgoody

samgoody — Tue, 20 Jan 2009 09:37:40 +0000

Nice comparison, though it must be updated to include Sizzle, and some note should be made that Dojo's engine is heading out as they adopt Sizzle as their own. A ways back Ajaxian posted about a selector engine called Peppy, which claims to outpace Moo, Sizzle, and everyone else. They have a version of slickspeed whith Peppy, Sizzle, Moo, et al. and it looks like they have something there. Do you (Aaron) or anyone else know what the raw deal is with Peppy, and whether or not they are what they claim. Peppy does use caching, and I gather that that messes up all the results, but is that his only gain? If so, why is their code not at least somewhat adopted? [I know that Moo doesn't use third party code, blah blah, and don't expect you to answer for Prototype, but as someone with a much better insight into the whole industry, you may have a thought that I completely missed.] Am including the links separately as I am not familiar with Wordpress' methods: Ajaxian article Peppy Comparison on the Peppy site