> It's like building a framework to simplify the SQL dialect. In reality, there's zero need for it

Years of people deploying web apps and using (My-)SQL without prepared statements provide a counterexample to this. One can argue about ORMs, but stating SQL would need no abstraction layer around it seems questionable to me :/

These are the same anti-Tailwind arguments that have been circulating forever.

If you want to build a case against Tailwind that's actually compelling, you should start by understanding what it is first. Only then can you compare it to other frameworks and methodologies.

I've made arguments like this in the past, and my position hasn't changed much

https://pdx.su/blog/2023-07-26-tailwind-and-the-death-of-cra...

Precisely this.

dont like "Cascading", inline css better https://vuejs.org/guide/scaling-up/sfc#what-about-separation...