Erik, you’re right that my argument is regarding cruft and the ability to write clean code quickly. JQuery does that really well, but performance is a big issue on the web too. That is the main reason why I chose to write the article, to show that jQuery can do some things much better than Closure, but that they can work together really well too. Using both libraries is less performant than just one, but it seems to be a good combination.

Closure is a great library. I’ve been meaning to write a revised version of this page to better, more evenhandedly, argue it’s merit. Closure isn’t designed to be heavy on DOM manipulation like you say, but it excels in other things (UI, Data Structures, etc).

Thanks for the feedback.

-I’m sorry, did you say ‘frames?’ Also, that is not true. There’s a second argument in the object wrapper called ‘context.’
-The arguments above weren’t comparing performance but cruft. I would not give Closure good odds in a performance-argument, however, and JQuery isn’t necessarily awesome on performance.
-It doesn’t need to. Even Crockford admits he’s hardly ever used his own widely published class system. Web UI is DOM-focused and event-driven with a framework of classes, IDs, and an SGML-based markup language to use for applying functionality. If you want a shortcut to writing your own class-based system, however, you may find JQ’s .extend method handy.

-I’m sorry, did you say ‘frames?’ Also, that is not true. There’s a second argument in the object wrapper called ‘context.’
-The arguments above weren’t comparing performance but cruft. I would not give Closure good odds in a performance-argument, however, and JQuery isn’t necessarily awesome on performance.
-It doesn’t need to. Even Crockford admits he’s hardly ever used his own widely published class system. Web UI is DOM-focused and event-driven with a framework of classes, IDs, and an SGML-based markup language to use for applying functionality. If you want a shortcut to writing your own class-based system, however, you may find JQ’s .extend method handy.

Just to make a few points:
- Google's Code is designed for use across multiple frames while loading the library only once where you have to load jQuery in every frame.
- If you want to play fair, compare the code that the compiler produces and not the actual source code
- jQuery is primarily designed for DOM manipulation not for complex things (it doesn't even have any notion of inheritance, or classes built-in)