Maybe it’s because I’m a bit of a control freak, but I can really empathise with what Lea is saying here: sometimes the developer convenience you get from using someone else’s code can result in quite a bit of redundant code. I feel that this is particularly a problem on the front end.
I completely agree with everything Rachel says here. I see far too many projects that start out with pre-emptive conditional comments, JavaScript libraries and polyfills, without knowing whether or not they’re actually going to be needed.
Lots Of Copies Keep Stuff Safe — a digital preservation initiative based at Stanford.
A detailed comparison of jQuery and MooTools.
Google is now hosting all the major JavaScript libraries. The caching benefits should be good news for your users.
Simon's slides from his talk at XTech on JavaScript libraries (which I missed). Good stuff contained within.
How much page weight is being wasted on JavaScript. It's time to shed those pounds.
Dan Webb does an excellent job of comparing the big four JavaScript libraries that were discussed at @media.
Cameron shares his thoughts on Ajax, Hijax, libraries and having fun.
Douglas Crockford proposes an acid test for JavaScript libraries - "If JSLint finds problems in a library, then dump it and move on to the next one."
This is the plain vanilla look.
You can subscribe to the RSS feed of links.