I think you missed the point of Tailwind, which is not to be an end-all be-all and replace CSS, it's just a utility library to replace/reduce the size of repetitive one-off classes. Nothing prevents you from using a CSS file for the more complex things you listed (which you should do), and Tailwind doesn't claim to replace all those parts of CSS.
The reason people think tailwind is supposed to replace CSS is the way adam wathan and the tailwind fanboys position it that way. There's a lot talk about how terrible css is from that camp.
Honestly, a lot of the negative sentiment comes from how the tailwind 'community' acts and positions themselves.
The tailwind home page feels tamer now than before, but the tone is still there.
Adam’s replies on twitter have always been a problem. I’m not going to go searching old tweet replies, so you can think I’m talking out of my ass if you want. But the guy is an ass. A lot of the responses to even neutral articles were whining manbabyish stuff (yes that’s subjective opinion). I haven’t seen it lately, so I’m hoping someone had a talk with him.
I do want to reiterate that I think tailwind itself has some great ideas. And there’s nothing wrong with utility css, if you’re not using a library you’ll end up writ a lot of it yourself.
