[joshuacc]

I haven't used Tailwind in a larger codebase, but it looks to me like the problem here isn't with Tailwind, it's with the lack of abstraction in the HTML.

The tone of the article rubbed me the wrong way as well. Pointing to a couple of examples of bad Tailwind usage and then making the sweeping generalization that using Tailwind is equivalent to "the death of web craftsmanship" is completely over the top.

Sure, using Tailwind means that you won't have lots of one-off "craftsmanship" in writing CSS. But that doesn't mean there's no craftsmanship. It just means that the focus of the craftsmanship moves from writing nice CSS to designing nice boundaries between your HTML components.

But what do I know? I've only been writing semantic HTML and CSS professionally for 18 years.

[CSSer]

You're not crazy. I've used Tailwind to accomplish 75% of the work required to rebrand an enterprise website with over 6k pages of unique content by updating only the Tailwind config. It's not perfect, but it's a reliably productive enough system as far as I'm concerned.