Tailwind is Great. Tailwind Sucks.

A balanced assessment of Tailwind CSS after three years of professional use, covering both its genuine strengths and real drawbacks. Pros include locality of behavior, eliminating naming overhead, natural design consistency through a token system, no CSS specificity issues, and minimal production CSS output. Cons include noisy markup that buries important attributes, a steep learning curve with inconsistent naming conventions, leaky abstraction requiring inline styles for dynamic values, dependency overhead, and a mandatory build step. The post concludes with practical guidance: Tailwind is best suited for teams prioritizing speed and consistency, using component-based frameworks like React or Vue, and working in standard web environments — but less ideal for highly custom or experimental CSS work.