4 ms·
With my rose tinted glasses on I would start to agree, but then I remember all the excess HTML it involved trying to do anything. Once you become accustomed to
by pull_my_finger 4y ago
With my rose tinted glasses on I would start to agree, but then I remember all the excess HTML it involved trying to do anything. Once you become accustomed to it you can get a pretty quick flow going, and I appreciate what it did at a time when the space was young, but I definitely don't want to go back to bootstrap in 2023.
- gedy 4y agoKinda confused if we're talking about Tailwind here, it's basically the same markup as Bootstrap or whatever would be. Ironically, markup is why I still prefer Bootstrap in 2023, because there's React/Vue/Svelte component libraries for it, and components are single tags: <Card>, <Alert>, whatever.
- pull_my_finger 4y agoThe difference is which markup in my opinion. You add a lot of utility classes in Tailwind etc, but with Bootstrap you actually have to add scaffolding elements to make things work. The obvious one is all the nested .container, .row, .col, but even trying to use the navbars or button groups etc all required a lot of specific incantations/boilerplate to use their components correctly. It's been years since I'd used it, maybe that's improved.