In my anecdotal experience using bootstrap correctly with enduser efficiency in mind is the exception, not the rule.
>Reflects poorly on those people then, not Bootstrap.
Yes.
>Of course, who wouldn't plan their project ahead of time?
Again, in my experience: MANY people using bootstrap
> The ones that don't need breadcrumbs?
> // @import "bootstrap/breadcrumbs";
> ...aaand we're done.
My comment was pointing out an inherent flaw to the popularity of bootstrap (which is no fault of their own): it's often used improperly and has lead to MASSIVE amounts of resources being wasted globally.
My comment was made with the hope that someone who hadn't previously thought about WHY they are using bootstrap to think about it a little more at the start of their next project.
You decided to respond by essentially fulfilling the stereotype of "condescending IT guy."
I'm happy that you know how to use bootstrap as intended, and I apologize if my comment upset you... but I don't see the need to be a dick about it.
I'm sorry you took offense, I'm not sure what you found condescending.
If someone uses a hammer instead of a screwdriver we don't blame the hammer.
>in my experience: MANY people using bootstrap
Sure but you said "YOUr'e" sacrificing efficiency. If you want to move the goalposts to "using Bootstrap incorrectly is inefficient" it will be a different discussion.
I agree, we should use tools correctly, but the comment I responded to (and the crux of the discussion) revolves around the suggestion that removing Bootstrap "led to a better website".
>most people using bootstrap probably don't need to
Reflects poorly on those people then, not Bootstrap.
>I'd recommend questioning it at the start of every project
Of course, who wouldn't plan their project ahead of time?
I mostly work on enterprise-level sites, every one has a modal, a dropdown, etc. I have yet to work on any site that didn't need a grid.
The ones that don't need breadcrumbs?
// @import "bootstrap/breadcrumbs";
...aaand we're done.