this post was submitted on 20 Sep 2026
4 points (64.3% liked)
Programming
28751 readers
646 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Tailwind class soup is something I see often in LLM-generated code. For some reason, every starter template in existence decided to include Tailwind, and then the coworker generating this code (who doesn't have frontend experience at all) just rolls with whatever the LLM shits out.
I believe there's a proper way to use Tailwind, but I can't be bothered to read the docs for it. It makes far more sense to me to either use plain CSS or, if I'm using a component library, then whatever that library comes with for its theming system.
Also, this whole article basically boils down to "use a proper theming system", which it even admits can be as simple as some CSS classes with standardized names.
Eh, if you’re using React or any other modern app framework (or “library” as they call themselves) then Tailwind classes are nicer for co-locating styles with their respective components. Vue lets you co-locate the actual style block, but even that’s not as nice as seeing the styles directly on the elements themselves. There are still uses for global-level CSS of course, but there’s no “central” place for those besides the html tag.