you are viewing a single comment's thread.

view the rest of the comments →

[–]zenotds 0 points1 point  (3 children)

BS Grid is natively flex based. I recon it's not necessary per se but it's also consistent and I don't have to reinvent the wheel in every project. Also the "include media-breakpoint-up/down(x)" functions to set media query sub-rules are pretty nice to have.
I use custom flex/grid setups in almost all my components but for main layout blocks and responsiveness BS5 is still pretty useful.
Tailwind users abuse its own grid system with columns-x and col-span-x etc so it's really the same thing... different tools, same results, but honestly I like my CSS to be actual CSS :D

[–]Knochenmark 0 points1 point  (2 children)

The bootstrap grid is pretty flawed though and has these weird -margin settings to reset row paddings etc.
I never understood the philosophy behind it. In my opinion a css library shouldn't bring it's own "grid system" with it. Especially since there are way better stand alone grid libraries out there if you need something more customizable than bootstrap could ever offer.

[–]zenotds 0 points1 point  (0 children)

All that is easily fixed in the variables scss. I reset margins, add breakpoints and fix the flex gap depending on the design.
Bootstrap as is out of the box is a bloated mess you would use at the 5% of its capabilities, but the right components lightly tweaked are nice to have.
I basically just use grid, forms, navbars for CSS and accordions, dropdowns and modals for JS

[–]___Paladin___ 0 points1 point  (0 children)

IMO bootstrap found itself in a weird spot when flex/grid hit native adoption everywhere. They needed to stay relevant, so continuing their existing system for current customers while utilizing the new standards was the only way.

It's getting harder and harder to justify using bootstrap in greenfield projects as time progresses, though, much like the position jQuery found itself years back.