Tailwind reminds me a lot of email CSS, where all styles must be inlined. But just more terse.
I prefer SCSS, having used both as well as Bootstrap, just because I don't think Tailwind adds much more than it takes away.
CSS has slowly been creeping up on the frameworks too, providing native layout implementations that erode the benefit of frameworks.
But there's data in the widespread uptake of Tailwind. CSS purists need to understand why it has been so widely adopted, rather than just saying it's the wrong way to do things.
Because the truth is, in a typical development organisation, SCSS turns to mush just as quickly and easily as Tailwind does. Perhaps you can argue the mush is better because it's separated from the HTML instead of exploding class attributes.
But since Tailwind has a dev speed advantage, it's still ahead.
There's also data in what became the most popular CSS framework: BEM. This was specifically designed to contrain the cascade depth of CSS, one of its biggest problems from a maintainability perspective.
There's a saying that "one should program INTO a language, not WITH it", which I think rings true here.
It's not about Tailwind vs whatever. It's about what are the actual problems we are encountering with styling, especially at a birds eye perspective of years and organizations, rather than me and now, and how would we address those from first principles.
Not: pick a book off a shelf and call it gospel.