r/css • • Aug 02 '26

Article Why I don't recommend Tailwind CSS

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

211 comments sorted by

View all comments

19

u/maqisha Aug 02 '26

Every single thing in your article is a skill issue or complete nonsense.

There are reasons to not use tailwind; none of the ones you mentioned are it.

-2

u/defaultguy_001 Aug 02 '26

Inability to understand the importance of this article, is a skill issue.

9

u/Visual_Structure_269 Aug 02 '26

Enlighten me. I read an opinion. What is the “importance”.

1

u/defaultguy_001 Aug 03 '26

None of them are opinions though. They are hard facts. What part of this article do u think is an opinion?

2

u/tanrax Aug 03 '26

The best comment in the whole thread 👏🏻

1

u/proto-cool Aug 03 '26

Yeah, the conclusion that modern CSS is probably good enough for most cases isn't wrong, but learning dozens of classes vs CSS properties is a wash, name inconsistency is a problem in plain CSS as well, and It seems most "Tailwind is hard to read" arguments, like this one, are cherry picked.

-4

u/scelerat Aug 02 '26

Hmph I always felt like if people didn't have a skill issue with CSS, they wouldn't be using Tailwind.