CSS are really powerful.
The real pain is how to organize them and mix a semantic approach with a declarative one.
The Tailwind model is winning because it's easy on this regard.
(I don't love it, but started to appreciate its strengths)
Discussion
Yes, it takes a while to find your groove. I really dislike Tailwind. I understand the intent of attaching style on a component-level directly in the markup and how that can be helpful for larger teams/projects. But it is just so ugly and hard to read. Just feels like it's an abstraction layer for people who either dislike CSS or don't want to properly learn it. And why not use CSS directly instead of a slightly different vocabulary for it that is much harder to read? A nice separation between structure, style, and function is so clean, and frameworks like Vue also provide nice encapsulation.
/End of rant and for anyone who loves Tailwind, that's great for you.
I essentially agree.
For me, the main pain of Tailwind is the total mess that it causes with git. Having all the classes inline, it is basically impossible to diff and have a clear picture of what have been done in a commit.