Crockford doesn't work on YUI - but he does work at Yahoo. I will fully concede that he may know more about ECMAScript than me - but I will happily challenge hi

Crockford doesn't work on YUI - but he does work at Yahoo. I will fully concede that he may know more about ECMAScript than me - but I will happily challenge him on JavaScript + DOM any day :-) Quite seriously though, since jQuery and YUI came out at nearly the same time back in early 2006 - I feel that it has to do with the simplicity of the jQuery API and the active community that's grown around jQuery. YUI has always had better documentation (even though jQuery's has been good), so that can't be it. A couple points: - You can always do more complicated work with simple APIs but it's fundamentally harder to do simple work with more complex APIs. - YUI didn't promote external plugins or development communities. For example the ExtJS library that grew up based upon YUI was left to stagnate and grow on its own rather than become part of YUI itself. If the YUI team worked to bring Jack Slocum on board YUI would be in a much more dominant position than what it is now. - YUI has been closed to outside contributions for most of its life. No bug tracker, no outside patches, etc. It's only recently that they've truly Open Sourced both the code and the process surrounding the library. I do find it to be odd, as well - YUI really should be more popular than it is. It's well written, well documented, and is well maintained. Even after all of that its market share is shrinking. http://google.com/trends?q=jquery+javascript%2C+yui+javascript http://google.com/trends?q=jquery+javascript%2C+yui+javascri...