I’ve been using it for a few years now because it makes the front-end work less time consuming. Out of the box, it just supports 4 sizes natively. It works well with modal windows, forms, grids and several other commonly used parts of a website.

Overwriting the default styling is easy enough. It works well with SASS. And I’m using a CDN with fallback to self-hosted Bootstrap source files. Mostly, the size of the framework doesn’t matter to me.

The requirements of classes in HTML and the lack of actual semantics. Mostly. It’s there, ish. But then again, who cares? Does Google care? No, they don’t really care. I’ve had HTML4 websites full of actual table-based layouts top the search results.

Screen readers for the visually impaired? Maybe. I don’t test for those. I’ve worked on a website with tens of millions of unique visitors a day and they didn’t really care, even though they cared about IE6 back in 2011 because they were 2% of their income (still several millions a year).

I’d like to do away with Bootstrap, though. Mostly because I feel that I could reduce my website initial load size by another 40KB. That’s worth it for people on crappy mobile connections. Ish. I mean, is saving them a few seconds of load time (which they are already expecting because of a crappy connection) worth wasting several hours of extra work every month?

Doubt it.

As long as it has no clear massive downsides and oversights I’ll stick with it. Most of my end-users have a western European high speed internet connection that’ll load and render the page to appear ready for use in less than a second.

That’s blazingly fast. With Bootstrap. Which I’m happy enough with. For now.