[bdr]

As a counterexample, I just built a site with Bootstrap, and I was very happy with the experience. It's the first site I've ever made that I think looks pretty good.

I worked around the styles I didn't want in two different ways. One, I built my own version of the css that excluded all the form styles (non-native controls are bad). This involved installing some packages that I didn't really understand but didn't need to. It took maybe five minutes start to finish. The second was simply overriding the CSS I didn't want. This is absolutely no different than what you do with any other website, where you're overriding the browser's default styles instead of Bootstrap's.

[jonmc12]

"This is absolutely no different than what you do with any other website, where you're overriding the browser's default styles instead of Bootstrap's"

Its different. There are all kinds of properties I don't want to have to override. This gives me the option of deleting code from bootstrap css or having duplicate css code in my project, every page load, and every rendering of the dom.

A prototype is fine, but once I'm working with a graphic designer, its mostly undoing vs overriding. Would be so much more bootstrap-able if the styles were constrained to classes.

[asifjamil]

I agree. The problem I'm facing now is that I customized a lot of the CSS styles directly, but with the new ongoing updates, it's not going to be easy to merge them through.

[bdr]

Deleting code from Bootstrap isn't a big deal, neither is having duplicate CSS. I'd rather do that than stick dozens of little classes everywhere. FWIW, if you prefer the class approach, it's probably not too big of a change to the .less files.