I agree wholeheartedly, however some of the re-use headaches of using a framework with non-semantic class names can be mitigated if you're using some sort of in

I agree wholeheartedly, however some of the re-use headaches of using a framework with non-semantic class names can be mitigated if you're using some sort of include/templating layer (see my other post in this thread.) Done well, on a site with a fairly standardized design from page to page, you'd hopefully only have to edit the markup and/or class names in a few included files, and then the external CSS. This of course isn't going to help you if you inherit a mess, and you'd be better off just using "content descriptive class names" in the first place, but it can be an option.