[vehemenz]

A few counterpoints:

Treating markup and styles separately is great, in principle, but you'll always need additional markup for certain things. We knew this going back to the early 2000s.

There is nothing about Tailwind itself that forces you to use divs and spans instead of the appropriate HTML tag.

Documents and interfaces are different. Tailwind makes a lot more sense for interfaces. You can use Tailwind for the interface and scoped HTML selectors for other content.

Tailwind is around 4x faster and has practically no overhead compared to writing a complex CSS codebase. Whatever you think of it, this is always a benefit in its corner.

[TonyAlicea10]

Folks in this thread keep conflating “forces to” and “ergonomically encourages”.

If a power tool is poorly designed it may not force me to hurt myself but if it makes it easier that’s a problem.

[fluffybucktsnek]

TBF, Tailwind is more about optimizing CSS sizes via the utility classes approach IIRC.

[hahn-kev]

I always feel like the distinction between interference and document is missing in these types of discussions. Often times they're as different as native vs web dev and if you don't realize that then you're arguing about totally different things and nothing will make sense.

[efortis]

Benchmarks?

[spiderfarmer]

As someone who wrote CSS for 20 years and who was against using Tailwind because of “principles” I must say that Tailwind is just awesome. Every minute spent trying to make sense of the structure past you or your colleagues came up with is a minute that could be spent on something more important.

Every time someone says that Tailwind sucks, it’s like hearing the old me speak.

[ncphillips]

Same here. It’s super weird take to me now. Maybe if you’re just writing plain HTML and CSS tailwind would be worse, but assuming there’s a component system you’re going to be just fine. The cascade of CSS is such a foot gun. Localized styles work great and tailwind abstracts away hardcoded values with relative ones

[paulhebert]

I prefer writing plain CSS over Tailwind

But I get component-scoped CSS (via Vue) and use custom props to abstract away hardcoded values

Tailwind isn’t the only option for those features