I tend to have a problem with the article you point to.
Part of the issue with ORMs is that they're hiding the way the data is stored to the developer, and they invariably strive for cross-DB functionality.
The first leads to mindlessly trying to hydrate the data, even if the underlying model is ccompletely broken. This introduce many bottlenecks in the process because it's bloody difficult to get either right. (Some have called ORMs the Vietnam of computer science.)
The second invariably leads to forgoing treats like domains with type checks, triggers, pl functionality and all sorts of things which, while in a different language, really belong in the database itself.
The end result is that ORMs will indeed suck (Data Mappers suck less), and ultimately convinces some users that ACID can be discarded, and RDBMS along with it. Go NoSQL. Err... Not. :-)
NoSQL has its uses, don't get me wrong. As a massively scalable cache, for instance, it's fantastic. :-)
Anyway, you might find these two discussions interesting, if the other side of the argument interests you: