Tailwind CSS
Utility-first CSS framework for styling HTML directly with composable class names.
HN commenters like it for keeping styles next to the markup they affect12, consistent utility classes across projects, comfortable everyday ergonomics345 and how easily LLMs write it.678 The most common complaints are cluttered, class-heavy HTML and unintuitive shorthand names that send even experienced CSS writers to the docs910111213, with some calling it a less powerful layer of indirection over plain CSS.141516
Why people recommend it
Ergonomics · 3
Experienced CSS writers say it is pleasant to use day to day and remains their go-to.
“I’ve also been writing CSS professionally for nearly 20 years and am a big fan of tailwind.”
“tailwind is still my go-to”
Show 1 more
“I love tailwind and will continue to use it”
LLM-friendly · 3
AI coding tools generate Tailwind well, which led some to adopt it.
“LLMs write Tailwind easily, so that's good.”
“I ended up switching, even though I still kind of loathe the class soup.”
Show 1 more
“My current stack is Astro/Next.js + Tailwind + TypeScript”
Locality and consistency · 2
Styles live with the markup and the same classes carry over from project to project.
“the classes are the description of the style once you know tailwind, and they live where the thing they're styling is.”
“CSS with Tailwind and JS with Alpine makes for pages that are mostly "self contained"”
Guardrails for teams · 2
It helps contributors of varying skill write correct, consistent CSS.
“I quite like Tailwind. I've had great experiences with it, especially on projects where the skill level of contributors was highly variable.”
“You use Tailwind in the same way you use BEM: becuase it makes it easier for frontend developers to write correct CSS.”
Server-rendered stacks · 3
Commenters pair it with htmx, Alpine and server-side rendering.
“htmx+ tailwindcss is the one combo that is right and I use it”
“Being a big fan of the server-side rendering, HTMX, Tailwind CSS, and Alpine.js”
Show 1 more
“CSS with Tailwind and JS with Alpine makes for pages that are mostly "self contained"”
Bootstrap alternative · 2
Seen as lighter and more customizable than Bootstrap, with unused classes removed at build time.
“The biggest disruption they personally did was offering a better alternative to Bootstrap.”
“Initially we used Bootstrap for responsive design, but later switched to a lighter TailwindCSS framework.”
Caveats and dissent
Class soup · 3
Long utility class lists bloat HTML and make it hard to read.
“I used Tailwind in one web based product and it was alright, but I'll never go back to using it.”
“I ended up switching, even though I still kind of loathe the class soup.”
Show 1 more
“It gets worse”
Unintuitive names · 3
Some utility names do not map clearly to CSS properties, so users keep looking them up.
“I love tailwind and will continue to use it”
“I used it for months at s previous job and spent a lot of time googling “how do I write X CSS property in Tailwind””
Show 1 more
“My team uses tailwind, therefore I use tailwind”
Weaker than CSS · 3
Critics see it as an indirection over CSS that gives up some of modern CSS's power.
“I quite like Tailwind. I've had great experiences with it, especially on projects where the skill level of contributors was highly variable.”
“It's a layer of indirection for no reason if it's the same.”
Show 1 more
Responsive styling · 1
One fan finds responsive styling the most awkward part.
“I’ve also been writing CSS professionally for nearly 20 years and am a big fan of tailwind.”
Less needed with AI · 1
One commenter says AI tools make maintaining a plain CSS design system easy enough to skip it.
“I used to use tailwind a lot, but AI has made it redundant largely.”
Often compared with
1 moved from Bootstrap to Tailwind CSS
1 moved from Tailwind CSS to Pico CSS
Who recommends it in their own words
From the makers not counted in the ranking
“We love python, react, tailwind, OpenAI, Google Cloud, and Claude Code.”
Threads where it came up
- Shopify acquires Tailwind 11 mentions
- I don't recommend Tailwind CSS 8 mentions
- Moving away from Tailwind, and learning to structure my CSS 5 mentions
- Creators of Tailwind laid off 75% of their engineering team 4 mentions
- Tailwind and Slop Apps 2 mentions
- Ask HN: What Are You Working On? (Nov 2025) 2 mentions
Also written as Tailwind. Data: tailwind-css.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 42
“CSS with Tailwind and JS with Alpine makes for pages that are mostly "self contained"”
“I use Tailwind with Nitro on a daily basis.”
“I use Tailwind because of components design”
“tailwind ui crap (solvable in minutes with css)”
“Tailwind is a hack”
“I've been using tailwind with svelte at work for years now and really like it”
“LLMs write Tailwind easily, so that's good.”
“I used it for months at s previous job and spent a lot of time googling “how do I write X CSS property in Tailwind””
“I love tailwind's work”
“I used to use tailwind a lot, but AI has made it redundant largely.”
“I love tailwind and will continue to use it”
“Tailwind is a great css framework”
“tailwind is still my go-to”
“I quite like Tailwind. I've had great experiences with it, especially on projects where the skill level of contributors was highly variable.”
“The biggest disruption they personally did was offering a better alternative to Bootstrap.”
“I used to gripe a lot about how Tailwind docs didn't play well with doc aggregators like devdocs.io”
“Tailwind CSS, Styled Components, Material UI”
“Being a big fan of the server-side rendering, HTMX, Tailwind CSS, and Alpine.js”
“I take issue with the core promise of Tailwind - localization of styles on a node.”
“I recommend it for certain situations.”
“You use Tailwind in the same way you use BEM: becuase it makes it easier for frontend developers to write correct CSS.”
“It's a layer of indirection for no reason if it's the same.”
“I switched from Tailwind to plain CSS with a UI library and it honestly made my site look better.”
“Tailwind is genius.”
“I use @apply in quite a few projects, mainly because I like the defaults in tailwindcss.”
“I use Tailwind for work and hobby projects”
“htmx+ tailwindcss is the one combo that is right and I use it”
“But, oops! Tailwind needed.”
“I wanted to use Tailwind/Shadcn”
“I wanted to give it a try, but didn't really click with it.”
“the classes are the description of the style once you know tailwind, and they live where the thing they're styling is.”
“I use tailwind for everything, and it doesn't look like this.”
“I ended up switching, even though I still kind of loathe the class soup.”
“painful deviations like React, Tailwinds, NextJS, I've learned them all”
“If you use tailwind, that's a sure sign you don't understand css.”
“I’ve also been writing CSS professionally for nearly 20 years and am a big fan of tailwind.”
“We also moved away from Tailwind”
“I used Tailwind in one web based product and it was alright, but I'll never go back to using it.”
“Tailwind is really nice as higher-level building blocks and saves me from writing a bunch of media queries.”
“modern styling with Tailwind CSS”
“My current stack is Astro/Next.js + Tailwind + TypeScript”
“My team uses tailwind, therefore I use tailwind”