It's true that you lose some semantics when using a utils-based approach like with tailwind. However, this can be compensated with components. A large portion of dynamic webpages uses UI libraries like react so this could be moved to a component and it would be easier to understand where we are.
Well for me it's even worse, as meaningful components are usually at lease twice as large as an example. And you get all this gibberish in classnames. Combine this with some developers that prefer div over any other tag and you get a very nasty unreadable combo with any ui library.
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.
It's true that you lose some semantics when using a utils-based approach like with tailwind. However, this can be compensated with components. A large portion of dynamic webpages uses UI libraries like react so this could be moved to a component and it would be easier to understand where we are.
Well for me it's even worse, as meaningful components are usually at lease twice as large as an example. And you get all this gibberish in classnames. Combine this with some developers that prefer div over any other tag and you get a very nasty unreadable combo with any ui library.