Right, that is understandable. However, my underlining objectives in
my applications are to achieve efficiency and performance, especially
over a browser executing JS where there are varying computers and
browsers. That usually lends itself to the people in charge of a
framework. Once I begin to adopt a framework and my applications
consume it, I hate having to port my code, so I always spend a lot of
time making a decision.. the hard part is to look ahead and consider
which framework will last.

Mootools has an interesting test suite comparing the various
frameworks: prototype, mootools and jquery right in your browser.
http://mootools.net/slickspeed/

These are older versions so I copied the test code and posted it on my
server with the latest versions of each framework: http://nulayer.com/~peter/jstest/

... I like jQuery, and I'd prefer to use it because of its adoption
and support, but from this small subset of a test, it does not perform
well at all. Reading the jQuery blog, they've taken on a developer to
optimize their code, I'm looking forward to seeing what they come up
with.

Regards,

Peter