I recently listened to the interview of Jeff Croft on boagworld. I had heard before that blueprint (and other CSS frameworks) were considered anti-semantic. I understand the gripe…but, is it really worth not using? I’ve used it a couple times now, and find it incredibly efficient.
And a little tip, it’s not that hard to keep semantic if you want to. My process, design & develop within the blueprint framework (if you want to argue that Blueprint limits your design, that’s a different topic). As you create your templates/pages, add an extra class name to your div’s (a semantic one, like say navigation). When your ready to go live, migrate the properties from the appropriate blueprint css classes into the new class names you created (shouldn’t take more than an hour). I don’t see what all the fuss is about.
Dude you need to post more often!