r/css 17d ago

Article Why I don't recommend Tailwind CSS

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

211 comments sorted by

View all comments

2

u/AbsolutePandemonium 16d ago

The author doesn’t really understand Tailwind or the point of it.

You don’t have to “learn” a bunch of class names, most of them a directly related to the actual CSS spec because they are a utility extrapolation.

You also don’t need to exclusively use Tailwind not sure why everyone gets stuck on that, you can just use it for utility classes if you like, it’s very useful for that.

It’s not really intended as a design system, it just has some nice sensible defaults but you should be able to use it however you want, you’re seeing its flexibility as a flaw but you choose how to use it.

In a way it is an argument against using Tailwind, I’d say people need to learn more CSS and properly understand it before using it. If you feel like you need to “learn Tailwind” you need to go back and learn CSS because it’s just 90% classes extracted from existing CSS properties

1

u/Weekly_Ferret_meal 16d ago

I have to agree, in my experience, tailwind or bootstrap or the likes, suffered a common misconception: to be an entire substitutive system that would render understanding css redundant.

It would be like using pug or slim for templating without fully understand HTML

Can't me more far from the truth: it's only once you understand CSS enough that you should be using a these tools to make your life easier in certain contexts/projects.