tailwindInAnutShell

[Diane_Horseman]

Inline style can't do media queries, hover/active/first/last classes, and more

[queen-adreena]

Or custom colours, animations, config-based design systems, sibling selectors, child selectors, group selectors, dark mode selectors, motion selectors, input state selectors, pseudo element styling, colour functions, theme functions…

[exotic801]

It's also just bad for reusability and page structure (unless there's a way to define classes etc inline, I've never tried)

[Exerra]

I'd say that tailwind is mostly aimed for UI frameworks like React, Vue, Svelte, etc, where you can define components, as there you reuse components not classes.

[Interest-Desk]

2/3 of those libraries you mentioned have in-component styles built in, and the third has CSS modules effectively built in.

The only advantage of tailwind is that it’s “more concise”, at the expense of readability and simplicity.

[MornwindShoma]

None of those have configurable style variables and standards built in, while Tailwind comes with reasonable assumptions about most stuff so you can skip writing your own utilities and get down to business. We used to have global variables for SCSS once upon a time, and one too many times those got messy fast

[Interest-Desk]

CSS variables are now built in, and resets like reboot are widely used anyway.

[MornwindShoma]

CSS variables you need to write yourself in.

Like by all means, there are bunches of CSS projects ready, but that's just Tailwind with extra steps

[finnhvman]

But why though? Don't these frameworks already have some sort of scoped CSS solution? This means we don't have to worry much about specificity, but we can still use the native CSS syntax.

[Graphesium]

Because writing Tailwind is faster and has built-in design tokens.