First off, CSS libraries like Tailwind have absolutely nothing to do with the semantic markup of the HTML content, so bringing that up is a totally moot point.
As far as "better SEO" and performance is concerned, Tailwind, out of the box, removes any unused classes from the bundled CSS file, ensuring that only the classes being used are loaded by the client, resulting in significantly smaller bundle sizes. On top of that, every class that is bundled is reusable from anywhere that shares that stylesheet. The entire point of helper classes is that you're not having to reuse the same style properties, and therefore reducing the overhead of multiple classes sharing the same properties.
And you potentially avoid legal issues in future.
I'm not even going to bother asking what you mean by this, because this is obviously just a random thought you had that literally has no legs to stand on.
This is just such a poor, lazy, and elitist counter-argument to using a framework that genuinely solves a real-world problem for a lot of developers.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a bad take.
First off, CSS libraries like Tailwind have absolutely nothing to do with the semantic markup of the HTML content, so bringing that up is a totally moot point.
As far as "better SEO" and performance is concerned, Tailwind, out of the box, removes any unused classes from the bundled CSS file, ensuring that only the classes being used are loaded by the client, resulting in significantly smaller bundle sizes. On top of that, every class that is bundled is reusable from anywhere that shares that stylesheet. The entire point of helper classes is that you're not having to reuse the same style properties, and therefore reducing the overhead of multiple classes sharing the same properties.
I'm not even going to bother asking what you mean by this, because this is obviously just a random thought you had that literally has no legs to stand on.
This is just such a poor, lazy, and elitist counter-argument to using a framework that genuinely solves a real-world problem for a lot of developers.