4 ms·
Personally I've never understood why people would need bootstrap on a new project. Especially if you're able to use flexbox. If you have a decent practical unde
by charrondev 10y ago
Personally I've never understood why people would need bootstrap on a new project. Especially if you're able to use flexbox. If you have a decent practical understanding of CSS, you can write could use plain CSS and a couple of classes for various components with significantly less overhead than bootstrap. Its pretty similar to how I see jquery nowadays honestly.
- allover 10y agoWith Bootstrap you can just pick the parts you need (so there is no practical 'overhead'), and most sites will at the very least need a responsive grid, and Bootstrap's (3's at least) is excellent. I don't know why you wouldn't want to use it, or something very similar from another framework. Even with flexbox you'd still need to reimplement the 'different column behaviours at various breakpoints', which is non-trivial. Also there's the whole other-devs-understanding-your-code scenario 'oh this is Bootstrap, I know this'. It gives you conventions BEYOND just what raw CSS gives you, e.g. the Sass variables it exposes.
- SippinLean 10y agoBecause using Sass you can reduce all bloat by commenting one file full of @imports, and it's easy to get up and running quickly. Depending on the type of site (I do e-commerce) EVERYone wants a modal, a tooltip, etc; it's much faster to just style components that have already been tested at all breakpoints in all browsers than write your own.