# Tailwind CSS Hacker Approved page: https://hackerapproved.com/p/tailwind-css/ 267 people recommended Tailwind CSS in Hacker News comments, 97 had mixed feelings and 215 criticized it, November 2025 to October 2026. It was recommended in 12 of 12 months, in 72 threads. It does not meet the Hacker Approved badge rule. **Verdict:** Recommended for fast styling that stays with each component, sparing you from naming classes and working well with AI coding tools, though critics say it clutters HTML with class lists. Summary written by Claude from the comments below. Claude agents reviewed it against the quotes on 2 Nov 2026. ## Why people recommend it - Styles co-located with components (7 comments in the sample): "It makes styling much simpler and quicker (everything is co-located, no need to write selectors, no need to make up class names" ([source](https://news.ycombinator.com/item?id=46166367)) "A vocabulary for style colocated with the elements works far better than an ever growing list of continuously overidden rules." ([source](https://news.ycombinator.com/item?id=46489753)) "they're reaching for it because as front-ends get increasingly componentized, the cascade becomes less and less of a benefit" ([source](https://news.ycombinator.com/item?id=49629332)) - Stays maintainable on large teams (5 comments in the sample): "Tailwind is just awesome. Every minute spent trying to make sense of the structure past you or your colleagues came up with is a minute…" ([source](https://news.ycombinator.com/item?id=48160782)) "The common arguments against Tailwind usually derive from total ignorance of working with CSS on large scale projects with many team members." ([source](https://news.ycombinator.com/item?id=48161040)) "utility classes (and Tailwind, by extension) solve for project management or organization level problems, not styling problems directly" ([source](https://news.ycombinator.com/item?id=46707834)) - Works well with AI models (4 comments in the sample): "Extensive tailwind training data in the models. Sure there's something more efficient but it's just safer to let the model leverage what it was trained…" ([source](https://news.ycombinator.com/item?id=46206943)) "tailwind helps. It is same as AI prompting, but in a deterministic and fine-grained way. Bottom line - it reduces the time to build." ([source](https://news.ycombinator.com/item?id=49142390)) "Both of those goals definitely help the current era of agents by making it easier to find the rules that affect an element" ([source](https://news.ycombinator.com/item?id=50249175)) - No need to name classes (4 comments in the sample): "the beauty of Tailwind is, when you actually do need themes, that's the only stuff you have to name and organize in separate CSS files" ([source](https://news.ycombinator.com/item?id=46572956)) "tailwind frees you from having to spend excessive time building abstractions of styles/classes that will invariably change" ([source](https://news.ycombinator.com/item?id=48160947)) "Tailwind CSS is Python dictionaries where you don't create one user-order-deliver-date CSS class for every Noun you have." ([source](https://news.ycombinator.com/item?id=49142825)) ## What people warn about - Clutters HTML with utility classes (2 comments in the sample): "Handwritten CSS still offers more opportunities for optimization and keeps your markup much cleaner than spamming utility classes everywhere" ([source](https://news.ycombinator.com/item?id=46554306)) "The way it totally pollutes your html makes it seem like, while the benefits are impressive, they're not worth the collateral damage." ([source](https://news.ycombinator.com/item?id=47808188)) - Resembles discouraged inline styling (2 comments in the sample): "I saw some vibecoded Tailwind where each class was essentially equivalent to style="font-size: 4em; background-color: grey; display: flex" ([source](https://news.ycombinator.com/item?id=48169572)) "It just also happens to be bad practice, this style of development is the exact thing we told everyone not to do for two decades." ([source](https://news.ycombinator.com/item?id=48192412)) - Shortcut around actually learning CSS (2 comments in the sample): "I actually like tailwind as a solution. But it was always a short cut for people who didn't want to reinvent all the low level…" ([source](https://news.ycombinator.com/item?id=49627628)) "The pain point tailwind supposedly solves is that people who are supposed to be front end web developers don’t understand CSS." ([source](https://news.ycombinator.com/item?id=49637540)) - Less needed now AI writes CSS (1 comment in the sample): "Tailwind is really a developer convivence, it made things pretty fast to style…" ([source](https://news.ycombinator.com/item?id=46537536)) ## Other CSS frameworks people recommend - [Bootstrap](https://hackerapproved.com/p/bootstrap/): 54 recommend, 17 mixed, 37 criticize - [98.css](https://hackerapproved.com/p/98-css/): 35 recommend, 6 mixed, 4 criticize - [Oat HTML UI component library](https://hackerapproved.com/p/oat/): 22 recommend, 5 mixed, 11 criticize - [DaisyUI](https://hackerapproved.com/p/daisyui/): 20 recommend, 1 mixed, 6 criticize ## The badge A product earns the Hacker Approved badge when at least 10 people recommend it, recommenders outnumber critics at least 2 to 1 (mixed feelings count toward neither side), it was recommended in at least 4 of the 12 months and in at least 5 different threads, and no single thread supplies more than half of the people who recommend it. Health and money products are never badged. ## Cite as Hacker Approved, "Tailwind CSS", https://hackerapproved.com/p/tailwind-css/ (267 recommend, 97 mixed, 215 criticize; Hacker News comments, November 2025 to October 2026). Counts updated 2 Nov 2026, with data through October 31, 2026.