Separation of concerns violated by mixing styles with markup
3/10 LowTailwind mixes CSS styling concerns directly into HTML markup, violating traditional separation of concerns principles and resulting in code that looks like inline styles, which many developers find aesthetically unpleasant.
Sources
- The Tailwind CSS Drama Your Users Don't Care About
- Helper Functions
- Tailwind CSS is the worst…
- Tailwind CSS - Unveiling the Hidden Downsides
- Disadvantages of Tailwind
- I tried to love TailwindCSS, here's why I couldn't | Balazs Barta ∙ Design Technologist
- Why Tailwind Isn't for Me
- Why I still Choose Tailwind CSS in 2025
Collection History
Query: “What are the most common pain points with Tailwind CSS for developers in 2025?”4/5/2026
Mixes the ol' separation of concerns — styles with markup. It bloats HTML markup and looks like inline styles === ugly.
Created: 4/5/2026Updated: 4/5/2026