Reasons the author does not recommend Tailwind CSS

A recent post on Andros.dev titled “Why I Don’t Recommend Tailwind CSS” has sparked discussion in the developer community. The author, who has extensive experience building web applications, argues that the utility‑first framework can lead to bloated markup, difficulty in maintaining large codebases, and a steep learning curve for teams accustomed to more traditional CSS methodologies. The article cites specific examples, such as the proliferation of repetitive class names in HTML, the challenges of debugging styles that are scattered across the markup, and the potential for increased bundle sizes when unused utilities are not purged effectively.

The piece also highlights concerns about developer ergonomics. According to the author, the lack of semantic class names can obscure the intent of the UI, making it harder for new contributors to understand the structure of a component. Additionally, the article points out that the tight coupling between markup and styling can hinder the separation of concerns that many teams rely on, especially when working with designers who prefer to manage styles in dedicated files. While acknowledging Tailwind’s benefits—such as rapid prototyping and a consistent design system—the author concludes that the trade‑offs often outweigh the advantages for larger, long‑term projects.

The post has generated a lively conversation on Hacker News, where it currently holds 49 points and 40 comments. Readers have debated the merits of utility‑first frameworks, with some praising Tailwind’s efficiency and others echoing the author’s cautionary stance. The discussion underscores the ongoing debate over best practices in front‑end development and the need for teams to carefully evaluate the tooling that best fits their project’s scale and maintenance requirements.