Yes, of course, that would be a wise thing to do. No problem at all with that. But surely you can spare a few extra bytes by implementing your own, while still using essentially the same &quot;battle-tested&quot; Bootstrap approach.<p>Also, you wouldn&#x27;t be constrained. Bootstrap means a predefined set of breakpoints for responsiveness: you can change their values, but not their number - you&#x27;ll always get 4 breakpoints. Bootstrap also means a float-based  grid system; you may want a flexbox based solution if you&#x27;re targeting new browsers. And, of course, another pet peeve of mine: Bootstrap-powered HTML source-code looks all the same (a bunch of .row and .col.xs-N). Of course, you can use the mix-ins, but I think every Bootstrap user can relate: the mark-up for the user details page looks an awful lot like the order page. :) I actually prefer to write (and, even more, maintain) mark-up with semantic classes.<p>As I said above, it&#x27;s not a big problem and using only the grid is a wise thing to do. I just don&#x27;t think it adds that much; might as well implement it myself, targeted to my needs (and I&#x27;ll do it once or twice, then reuse).