While I don't agree at all with the idea of abandoning classes for clever ancestry-driven selectors, the author is absolutely right about the advantages of the

While I don't agree at all with the idea of abandoning classes for clever ancestry-driven selectors, the author is absolutely right about the advantages of the HTML5 content model and the portability of semantic markup. I wish more people would advocate for a middle ground between this content driven approach and an OOCSS approach. They work so nicely together. Who ever said that you should stop caring about using semantically correct tags when using portable classes for styling?