Mister Edwards: let all the libraries accidentally steal your code please.. Or am I missing something?

We took the opportunity to step beyond any previously-released speed test suites and improve the speed of the three most commonly used portions of jQuery: ID selectors, tag name selectors, and each() loops:
$(”#id”) : 1676% faster
$(”elem”) : 295% faster
.each() : 554% faster

Damn $(“#id”) is 10 times faster?! How could you get any faster than document.getElementById?

Together with the deep extend & noConflict, we can finally allow the ever popular:

/* jQuery lolcatz plugin 0.2b */
(function($) {
$.cheez = { taste: "delicious" };
$.extend(true, $, { cheez: { burger: "span" } } );
$$ = jQuery.noConflict(true);
})(jQuery);

Previously efforts to extend cheez on to burgers was destroying taste.
This plugin, soon to be released, allows guaranteed, no-conflict, cheezburger delivery.

now, we can work in style

$(‘div’).can.has(‘p’)

i’ve always wanted to be able to do that. thank you jQuery!.

@Rizqi:
In the event that jQuery is written into say, Firefox extensions, or if jQuery is loaded with GreaseMonkey, and then you visit a webpage ALSO using jQuery, the namespace prevents collision. You could also run two versions of jQuery, i.e. a stable version and a beta, for testing on the same html/js without making two separate pages. Or if jQuery is written into a Widget, and that widget placed inside a page which uses jQuery…. The list goes on

Additionally, it’s good because you can now inject jQuery into any web site, and it’ll still work. (Some people have written Firefox extensions to inject jQuery into random web pages – so this will help them.)

I was referring to the ability to embed jQuery into the namespaces of other objects and include multiple versions of jQuery on the same page.

Cheers,
Tara