How does it affect quality?
You're going to tell me next that you have a JSON interface instead. But that's a site-specific API that's designed for vendor lock-in. You're going to find that doesn't work and need to create a universal format. And now you have completely recreated the problem HTML was intended to solve originally.
All of this wasted effort that web Devs do doesn't come from nowhere. The people with slow browsers or accessibility needs are absorbing your productivity gains 1:1.
First, Tailwind has literally no opinion on whether your html is semantic or not. Second, it isn't "backed by javascript", that's nonsense and is just self-evidently not true. Third, "people with slow browsers" benefit because the CSS footprint is smaller. Fourth, the quality of the site improves with Tailwind because developers can spend their unused energy on other enhancements.
Why get on this thread and spew a bunch of bullshit? What's the point dude.
At least know the topic you criticize.
It’s as semantic as you make it. And it works without JS.
I know this cuz I was a big ra ra cheerleader for the semantic web 15 years ago.
But then I found it made no bloody difference in actually helping people.
I’d much prefer if we all spent our energy building better, smarter screen readers.
From what I've seen online using Tailwind over other frameworks like Styled Components, gives +5x speed ups. So it is not wasted effort.
> The code usually cannot be modified or even viewed in a readable form by users.
That's right, most of the time it is even minified. It' is not meant to be read by humans but by the browser. Poor accessibility is is a result of it not being prioritized designing/development of a product.