In the Q&A section of this talk, Douglas Crockford says that jQuery doesn't scale as well as some other popular libraries. What does he mean by that, and what is it about the other libraries that makes them more scalable?
If you watch the video, he doesn't talk about jQuery formally. It is a quick response to a somewhat offtopic question from someone after the presentation....at the end of the presentation, about minute 1:29.
He says a lot of good things about jQuery. The part about it not scaling well, he says he doesn't think jQuery scales very well for very complicated applications (comparing it to other things like YUI). .
Its hard for me to say without watching the video, but my guess is that it's because jQuery doesn't offer all the features of most other libraries that make JS programming easier. jQuery's purpose is to make DOM manipulation easier by simplifying addressing of elements via CSS selectors, and providing an easy framework for altering those elements. It offers some other feautes such as AJAX requests, basic event management, templating, and some other rudimentary functionality, but that's about it.
Other libraries such as Prototype, MooTools, ExtJS and Dojo provide loads of other functionality for creating objects, managing arrays & collections, manipulating strings, and doing all the other nitty gritty things that we as programmers expect to be able to do.
At least, that's what I think he means.
|show 3 more comments|
jQuery doesn't allow you a lot of reuse like MooTools for instance.
It's a philosophy/design decision: jquery not a lot of code for fire-and-forget scenario's
When you are building unobtrusive js experiences (usually only page enhancements) this works very well and requires very little code, when you build google docs... not so much. You will want more OOP concepts that other projects expose like inheritence, interface like mechanisme's etc...