I disagree with first quoted sentence below and the general premise of the article. True, Blueprint does force you to add some proprietary classes to your XHTML elements to dictate layout on a grid. But, your elements don't have to be divs, and you can still use additional classes to articulate the full semantic meaning of the element.

All in all, it's a small price to pay to speed up Web development. I have found I can whip up a nicely laid out site that works on all browsers *much* faster with Blueprint than I could without it. And, because there is a set of naming conventions, it makes it much easier for a team of developers (or if using a CMS, the content creators) to specify and read each others' layouts.

Quoted: A CSS framework passively removes a great majority of semantic value from the markup of a document and, in my opinion, should be avoided. This lack of semantic value works against a big part of what Web Standards are all about; creating documents with rich semantic value.