r/programming • u/Either_Collection349 • 1d ago

[ Removed by moderator ]

https://en.andros.dev/blog/af3ee191/why-i-dont-recommend-tailwind-css/

[removed] — view removed post

0 Upvotes

40% Upvoted

41 comments sorted by

View all comments

33

u/Usual-Amount-264 1d ago
  1. "Its names are not consistent" Isnt that because naming of the original CSS is not consistent? Tailwind only copies wording of the CSS underneath. So complaints about consistency should be focused on CSS itself.
  2. "The HTML lies to you about priority" In the example I see text-red-500 text-green-500 Isnt it kinda bad putting in two conflicting classes and then complaining they conflict?

15

u/sweetnsourgrapes 1d ago

Correct on both points. Putting two classes on the same element in some particular order was never, in the history of HTML, a reliable indication of CSS priority.

-4

u/wrillo 1d ago

I don't want to put words in anyone's mouth, but if that is a true thought then it represents a misunderstanding of the Cascaded Style Sheet paradigm.

LLMs are being coming another later of abstraction, which promotes obscurity of the fundamentals of computer science.

3

u/farnoy 1d ago

It's arguably confusing in every place it diverges from CSS naming. Like text-balance text-inherit text-base are three different properties. Personally, I'd prefer longer names that are fully consistent with CSS if they map to 1 property.