Yesterday, Ajaxian tells us that the Dojo Community will vote on whether they implement the Sizzle selector engine instead of using their own.

Just after reading that I thought whether MooTools would benefit from implementing a selector engine instead of using their own. Apparently I was not alone in this thought as Aaron Newton has posted his thoughts and pros/cons. Here’s my two cents.

Aaron brings up very good pros and cons. I think we should not follow the trend and switch to Sizzle but instead take in what we can and be inspired to improve upon it. We should already be doing that. This would require our awesome MooTools dev team to be up-to-date, but aren’t they continuously learning?

In this way, we can keep to the ‘extensibility’ philosophy. Besides, if we figure out an even better method, who is to say that other developers aren’t looking at MooTools and taking from it what they deem better?

Lastly, why Sizzle and not Peppy? Last I checked, Peppy was beating out Sizzle on SlickSpeed. James recently took a stab at documentation for Peppy too.

At the end of the day, it all depends on what our MooTools dev team wants to do because, after all, MooTools was created for their use, and it’s great if others can use it too.

P.S. Thanks to James Donaghue and John Resig on their awesome work!