Using a framework favors convention over configuration for the benefit of speed.
I especially like it because the team has a central set of documentation for the UI to use - that means if we override a style, if they followed the convention, everything works out better.
I do agree using a namespace would help though.
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.
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.
I'm really not sure I understand the strategy of dumping so many styles into the global name space. Basically, all of us have been working around the styling as we implement features.. a major refactor is in order and we will likely be ditching bootstrap.
Just a warning if you plan to build beyond the styles provided by bootstrap, it is not straightforward. Really, the entire set of styles should be contained within its own namespace or some other meaningful semantic convention.
Am I missing something? What is intended after 'boot'? am I really supposed to replace these global styles manually?