17

‘Hey let’s use bootstrap’
‘Hey let’s make it pixel perfect to this design’
‘Hey, lets completely ignore bootstrap when designing’
‘Hey lets pile it all on dev while he fights this framework for 8 hours a day instead of working to bootstraps limitations’
I wish people would just accept that if you use bootstrap, you have to let a pixel here or there go for the sake of responsiveness.

Comments
  • 5
    Could we make 2020 the year that we let bootstrap die?
  • 3
    Turns out, relative is relative. 👍
  • 4
    @odite
    Yes. There's just generally better things out there. Heard they were at least dumping jQuery though.
  • 2
    Why should I choose some other framework if bootstrap suits my usecases well?
  • 1
    @AndiLeni With modern CSS, I don't see the need for frameworks.
  • 2
    @odite in the end bootstrap is css. It just solves a few problems which I don't like to solve myself.
  • 1
    @AndiLeni
    Are you looking for an exhaustive list? Those are all over the internet.

    Big ones for most: Bootstrap is kind of outdated in terms of the quality of experience it can provide. No regression support past IE10 for bootstrap 4. Dependence on jQuery and now popper as well for plugins. No consolidated update model, so any significant number of simultaneous updates will risk screen thrashing or blowing the 100ms update usability rule. The flex implementation is an afterthought, and a poorly developed one that you would honestly be better off just writing the flexbox rules yourself.

    Tl;Dr it's really easy to deliver a poor user experience.
  • 0
    @AndiLeni If it fits your use case, go ahead. Honestly it’s good for making quick user interfaces, but css3 is so powerful that you can do practically everything bootstrap became famous for with relative ease.
    Css grid is objectively better than bootstrap grid which is what the majority of developers use bootstrap for anyway.
    Scss compiling a bootstrap theme (which is now pretty standard industry practice) basically makes the argument ‘well it doesn’t effect page speed because it’s cached’ redundant.
    The file sizes for the html documents are larger because of the significant increase in semantically pointless nested divs.
    And on top of that, the return in speed of development gets thrown out of the window when your design doesn’t completely adhere to certain rules, as you have to wrestle the framework into submission.
    But if you want to make an app with little to no actual css programming, then it’s a good fit.
Add Comment