Welcome to WebmasterWorld Guest from 184.108.40.206
Forum Moderators: not2easy
obviously bootstrap is somewhat bloated ... so i've (or anyone else has) two options, either compile a leaner and meaner version of bootstrap, using only the styles that i use - and serve it from my own server.Very bloated... that was the first thing I noticed when I started converting to mobile.
joined:Oct 2, 2003
... so I've (or anyone else has) two options
Actually, there is a third: stop using it.
Why Bootstrap Is Bad
- Bootstrap encourages the use of classes in a presentational manner,
which defeats the reason for keeping HTML and CSS separate.
- Bootstrap encourages the use of endless pointless redundant classes
with pointless divs, resulting in two to three times the HTML as one
would have without it, only further compounded by one having to write
as much CSS as one would have without the framework. If it saves one
anything in CSS, it only does so by making one write sufficiently more
HTML that it's awash. It's a step sideways on work and a step backwards
- Since it's use results in presentational classes and excessive div and
span elements, it is basically putting presentation in the markup where it
has absolutely no business. HTML and CSS are separate so one can
have multiple appearances, slapping a class in for each of those
possibilities is really nonsensical.
- The way Bootstrap works is as flawed as the new, allegedly structural,
tags from HTML 5. It undoes nearly twenty years of progress to the point
where one might as well go back to writing HTML 3.2 and pretending that
CSS never even existed. It can only make one's work harder.
- The HTML should say what things are, not how one wants them to look
like. By using classes to say what things are going to look like, one
violates that most basic rule of what HTML is actually for. That's why
OOCSS and the the frameworks based on that notion are utter rubbish.
- . If it looks simpler, one falls into the trap of false simplicity. It is as much if
not more work, resulting in one writing as much if not more code, not
counting the massive size of the framework against
it. The only way it could be 'simpler' or 'easier' or 'faster' is if one doesn't
know enough about HTML or CSS to to make a rational choice about
using a framework.