`rm bootstrap.css` look, a 100% reduction! And it led to a better website.
`gzip goodfile.css` and there's an improvement several times more effective than even the best minifier. And it keeps your source code legible in the browser and doesn't require a slow/buggy asset pipeline to test changes.
Yes, yes, I know minify+gzip can save like an additional 1% over what gzip alone does. To me, that's just not worth the cost to the developer.
You're sacrificing personal efficiency for bandwidth efficiency. You get to decide which is the best option for you and your users.
I generally share the opinion that most people using bootstrap probably don't need to. I'd recommend questioning it at the start of every project instead of assuming it's what a project starts with.
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".
With modern front-end framework you only include the parts you need. No one in their right mind would include all of it. You only include the code for the modal if you need it.
One of the main points of css optimization is not transfer size, but the time it takes the css engine to parse through a css file, and figure out where to apply those changes to the DOM.
I think that while the described "reminification" method may not make sense in practice (as other's have said running minification process multiple times will amplify minifier bugs), Optimizing CSS, removing unused rules, grouping similar rules, optimizing selectors etc... does make sense, regardless of reduction amount in comparison to compression.
`gzip goodfile.css` and there's an improvement several times more effective than even the best minifier. And it keeps your source code legible in the browser and doesn't require a slow/buggy asset pipeline to test changes.
Yes, yes, I know minify+gzip can save like an additional 1% over what gzip alone does. To me, that's just not worth the cost to the developer.