2 months ago
- Tailwind requires learning dozens of utility classes, slowing initial development.
- It breaks the separation of structure and design, bloating HTML and reducing readability.
- Class naming is inconsistent, causing confusion (e.g., items-center vs justify-center).
- The design system is not enforced due to arbitrary values, relying on discipline.
- It is not a good gateway to learning CSS, as it abstracts away fundamentals.
- Code readability suffers, especially without @apply, and HTML order does not determine priority.
- Debugging in Dev Tools is cumbersome due to class soup.
- Modern CSS now offers native features (layers, nesting, variables) that reduce Tailwind's necessity.
- The tool has costs that may outweigh benefits for medium/large projects.