with all due respect, this sounds like a misunderstanding of CSS frameworks, and not of Tailwind itself.
i came to this conclusion based on two things:
your opinion that "utility classes elements lose all meaning" is just a case of what you're used to. plenty of devs are the other way around. some will understand both.
frameworks are an opinionated implementation of frontend styling. you're not meant to have full control at the low level.
CSS frameworks are used to abstract basic concepts as utilities. everything from rounded corners to breakpoints is ready for you, allowing you to implement complex design in a safe and maintainable manner.
see these points from the Tailwind docs for some more answers:
There is no logic at this point. If you can understand what styles are applied to an element does not mean that you can understand what this element is. This is the main concern with tailwind.
I've never mentioned that we lack control or anything like that.
When you get more experience with larger projects you will see that maintaining mess like tailwind output does not worth the effort on the long run. It has only one use case – you write styles once and then never return to them.
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.
with all due respect, this sounds like a misunderstanding of CSS frameworks, and not of Tailwind itself.
i came to this conclusion based on two things:
your opinion that "utility classes elements lose all meaning" is just a case of what you're used to. plenty of devs are the other way around. some will understand both.
frameworks are an opinionated implementation of frontend styling. you're not meant to have full control at the low level.
CSS frameworks are used to abstract basic concepts as utilities. everything from rounded corners to breakpoints is ready for you, allowing you to implement complex design in a safe and maintainable manner.
see these points from the Tailwind docs for some more answers:
dev-to-uploads.s3.amazonaws.com/i/...
dev-to-uploads.s3.amazonaws.com/i/...
When you get more experience with larger projects you will see that maintaining mess like tailwind output does not worth the effort on the long run. It has only one use case – you write styles once and then never return to them.