> you find yourself overriding and customizing them to such a degree that it's more productive to just build your own "vanilla" components that are specific to the way your site or organization uses them, and then just ditch Bootstrap altogether.
This has been similar to my experience. Bootstrap can be overwhelming at times, and there have been a few cases where I had to solve buggy behavior by specific Bootstrap components by writing elaborate fixes that would not have been required had I used my own framework. From that standpoint, working on a time-consuming, yet practically throwaway-type site, Bootstrap was really frustrating.
I do really like the low-baggage approach of Initializr's Responsive configuration as well as the Responsive Grid System.
For small throw away sites I tend to have getbootstrap open and using Chrome debugger cut and paste the bits off CSS I need into my own project.
Things like the nav bar are really clever, but way too much for most of my projects. I like the button styles, but usually modify them... stuff like that.
This has been similar to my experience. Bootstrap can be overwhelming at times, and there have been a few cases where I had to solve buggy behavior by specific Bootstrap components by writing elaborate fixes that would not have been required had I used my own framework. From that standpoint, working on a time-consuming, yet practically throwaway-type site, Bootstrap was really frustrating.
I do really like the low-baggage approach of Initializr's Responsive configuration as well as the Responsive Grid System.