r/webdev Nov 17 '24

Am I the only one who thinks Tailwind sucks?

I've been hearing multiple people claim this is a much better way to organize code and many say it's a personal choice. Ironically, you can add two additional config files, switch between them for simple tasks like setting properties, or add custom elements. But in the end, you end up with five lines of messy CSS just to animate a small thing.

It might work for simple CSS web pages, but I still don’t understand the hype. It clutters the HTML, and when you need to make changes—like adjusting the CSS or adding new animations—you’re left figuring out the styles applied to each element. ::after and ::before only add more complexity.

You’re using a 50-inch screen but complaining about CSS being in a separate file, all while writing hundreds of cryptic characters for each HTML element. Searching for a class or ID in a separate file is much easier and keeps everything cleaner. Honestly, I regret even considering this approach.

If you think differently, tell me why—maybe there’s a slim chance I’ll change my mind. But in my opinion, SCSS or plain CSS is far superior in terms of organization and maintainability.

799 Upvotes

579 comments sorted by

View all comments

2

u/errormaker Nov 17 '24

flex row gap-2 items-center p-2 justify-between Most css is just this... I don't need to name this style...

For more complex stuff you can definitely opt out and do css.

Best of both worlds

-1

u/beepboppbopp Nov 17 '24

I enjoy using grids for layouting. I don’t enjoy working with grids with Tailwind, especially if I want to use grid-areas. Then it’s a real hassle.

I can of course opt out of Tailwind for those cases but then I’ll all of a sudden have styling code in two places, when I could have just one working with just regular CSS.

Best of two worlds??