[rozenmd]

Sure Bootstrap is better, for you.

Your postscript explains why: using the same "btn-primary" as every other user of the framework hints that you're not building something with its own visual identity.

For the rest of us, we throw that "bg-sky-500 hover:bg-sky-600 active:bg-sky-700 text-white px-4 py-2 rounded-lg" (or whatever color and shape matches our brand) into a component with a variant=primary property and call it a day. What developers actually see on a day-to-day basis is <Button variant="primary" />.

[stephenr]

> Your postscript explains why: using the same "btn-primary" as every other user of the framework hints that you're not building something with its own visual identity.

You know that bootstrap is trivial to customise right?

It turns out identifying primary and secondary buttons is a pretty standard thing in any kind of UI that has... buttons.

[fastasucan]

Cant you just customize the css of btn-primary?

[twelvedogs]

oof, that looks like absolute trash. i don't get why you want to use something less readable than css but to each their own i guess

[andrei_says_]

TailwindCSS is useful for applying styles to isolated components, in paper-shredder scenarios. Devs using it get to ignore the cascade, don't have to name things, and can use the predefined spacing and colors.

It is of course quite unmaintainable (good luck with updating the class soup for a bunch of components across a project).

I personally just ... cannot. CSS in 2026 is incredibly powerful and beautiful. Embracing the cascade allows for minimal CSS (see ITCSS methodology). Standardizing spacing and type with https://utopia.fyi is brilliant. Standardizing colors with custom props is trivial.

But, it seems that a lot of people are not paid to think about CSS. Tailwind embraces that. LLMs love it, because it reduces the complexity of pure CSS.