"But here's where things get interesting: some of the libraries, like jQuery, have added support for a whole bunch of extra selectors on top of those provided by the CSS specs, while others, like Dojo, have stuck to supporting standard CSS selectors only."

So the article is a pretty average overview of the idea of the forward-looking API. What is so awful about this article are the comments. Most of them are either nit-picking, and many show a complete lack of understanding about the point the author was trying to make. It disappoints me.

"After reading A List Apart's article about if zebra striping (Link) makes any significant impact on speed/accessibility, I thought I would knock a quick demo up of taking zebra striping a step further using the mouseover event of jQuery, to me this appears to speed up scanning of the data."

I was hoping someone would come up with some ideas after that article. And this is a pretty neat solution. I think something like this, combined with something like Dojo's FishEyeLite would kick some serious tail.

"jQuery seems to make you work harder to type less code, while Prototype seems to cost you a few more characters for a bit less density. With the exception of Prototype's class support, their feature sets are fairly equivalent"

Some great insight into the relative tradeoffs of two different JavaScript libraries. I enjoy to read a post from someone that didn't drink the Kool-aid when it comes to jQuery who sees the lack of functionality, reliance on third-party libraries, the danger of node-bloom, and the pain of state management as a tradeoff rather than a feature.

"Bad programmers aren't able to really understand the problem in all it's details. Because of this they tend to 'emulate' or 'simulate' it step by step (for example by looking how a human solves the problems the program should do and than writing a program which does it similar). But simulation isn't the same as creating a solution based on thorough understanding."

This is my new go-to resource for explaining the idea of good/bad programmers. It's a very short, very accurate explanation.