As for your other comments, you seem to have a far greater knowledge and skill level dealing with CSS than you let on. That's great for you, it must make doing frontend work a breeze - and maybe you don't need Bootstrap. Not everybody is so experienced though - and for them, Bootstrap can make life much simpler.
Separation of content and presentation sounds good, but a concrete example would be much more convincing. (I do understand the general idea, so pls don't explain it.) I think what I am hearing is that css styles should be applied to tags rather than classes, but am not sure.
I suppose your time would be better spent building a prototype of what you mean instead of wasting it here. One link is worth a thousand words. Do it right, put it on github, give it five years, and people will be laughing at bootstrap sites, while you are racking up consulting fees.
As much as possible, yes. Here's a good example of what I mean, although he makes the mistake of taking it to the other extreme ("you should never use a class for anything ever!"):
http://coding.smashingmagazine.com/2012/06/19/classes-where-...
>Do it right, put it on github, give it five years, and people will be laughing at bootstrap sites, while you are racking up consulting fees.
That seems like a rather unfounded assumption. There's already several other CSS "frameworks" that are better than boostrap. What is popular and what is good are seldom strongly correlated.
Basically, if I were to use bootstrap the process appears to be the following:
1. Destroy my templates by filling them with tons of garbage containers and pointless class attributes. 2. Our mockups now look like twitter. 3. The actual design gets done, and we have to go back and remove all crap we had to put in for boostrap to begin with.
Which part of that is supposed to appeal to me? Or is the intent to actually ship sites to customers looking like twitter and having horrible markup?