One reason tailwind feels awkward for many senior developers is that it's an imperative way to write a declarative language.
If you're used to working "with the grain of the web", that clashes with the mental model you have for CSS.
@adactio , as usual, says it best: https://adactio.com/journal/18982
@mxbck @adactio It's striking to me how much this does not resonate with me, and I don't mean this in a disparaging way. I just cannot fathom how someone could label Tailwind as "imperative".
From my point of view, Tailwind is basically CSS with the tiniest (but important) set of restrictions: you can't just use any amount of pixels as spacing, you cannot just use any hex code as colour, but other than that, you can pretty much do anything that CSS can do.
In other words: it is so far away from "saying exactly what you want the final pixels on the screen to be", I just can't see what would make someone describe it as such. Which generally means that I'm missing something, so the question is: what? Would love it if someone could give me an example of Tailwind code that exemplifies this.
Sophie Koonin
Max Böck
Sara Joy 
JS Karate
Vincent Tunru
Amber Weinberg