Tailwind CSS

“Both of those goals definitely help the current era of agents by making it easier to find the rules that affect an element”

“The pain point tailwind supposedly solves is that people who are supposed to be front end web developers don’t understand CSS.”

“They did an excellent job making it so you could pick and choose what you wanted, then theme all of it from your tailwind settings with ease.”

“there's huge advantages to having your styling be associated directly with your components, and Tailwind is a great option”

“they're reaching for it because as front-ends get increasingly componentized, the cascade becomes less and less of a benefit”

“Tailwind is more relevant than ever in web development, it's practically the native language for UIs in the LLM world.”

“Finding space in a development ecosystem to provide a set of purpose-built tools is a common and healthy software business pattern.”

“I've had great experiences with it, especially on projects where the skill level of contributors was highly variable.”

“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 CSS hackery”

“components and pages become self-contained. As such, changing them doesn't cause unintended side-effects to other pages”

“Tailwind does not really have this pattern of deterioration growing along both time and complexity, it stays consistent on both axes.”

“With Tailwind you never need to try to come up with a name for anything relating to style, you just use utility classes.”

“Tailwind CSS is Python dictionaries where you don't create one user-order-deliver-date CSS class for every Noun you have.”

“tailwind helps. It is same as AI prompting, but in a deterministic and fine-grained way. Bottom line - it reduces the time to build.”

“I use tailwind for everything, and it doesn't look like this. They're utility classes, you can do absolutely anything you want with them.”

“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.”

“I saw some vibecoded Tailwind where each class was essentially equivalent to style="font-size: 4em; background-color: grey; display: flex;"”

“I think a lot of websites lately work better with “locally scoped” styles as there are just so many different components”

“The common arguments against Tailwind usually derive from total ignorance of working with CSS on large scale projects with many team members.”

“tailwind frees you from having to spend excessive time building abstractions of styles/classes that will invariably change”

“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 that could be spent on something more important.”

“You can perfectly create an HTML document with semantic meaning and the add Tailwind just as any other CSS framework or pure CSS to it.”

“HTML+Tailwind is the only format where "looks roughly correct" and "is structurally correct" have the same probability.”

“The way it totally pollutes your html makes it seem like, while the benefits are impressive, they're not worth the collateral damage.”

“Started this whole thing off thinking I'd use Bootstrap, Tailwind, and other frameworks but it quickly became way to complex. Tailwind won the battle.”

“utility classes (and Tailwind, by extension) solve for project management or organization level problems, not styling problems directly”

“If you just paste an outerHTML from the dev tools, AI coding agents can immediately figure out what it will look like”

“better to have a little extra spaghetti in your html code than create a truck load of spaghetti in your app.css stylesheet”

“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”

“It’s more about cognitive load, and abstraction level. If you’re trying to make an object spin, it’s much easier to use the tailwind class”

“For me, shit like Bootstrap or Tailwind or whatever is nice. I have to spend less time fiddling with something I think is a waste of my time.”

“So I tried Tailwind and it seemed to help. But now that Claude Opus 4.5 is writing all my code, it can write and debug CSS better than I can use Tailwind.”

“Handwritten CSS still offers more opportunities for optimization and keeps your markup much cleaner than spamming utility classes everywhere”

“Styles-in-HTML (Tailwind): class="m-4 mb-2 p-2 border border-radius-sm border gray-200 hover:border-gray-300 font-sm sm:font-xs [...]"”

“Tailwind is really a developer convivence, it made things pretty fast to style, but now I don't really think it has anywhere near the advantages it did.”

“I've never been a huge fan of using Tailwind personally, but I deeply appreciated that they were making a (mostly) non-enterprise FOSS model work”

“I love Tailwind, and I am really sorry Adam and co are going through this. They've built a great product, and it's brought joy back building again for me.”

“A vocabulary for style colocated with the elements works far better than an ever growing list of continuously overidden rules.”

“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 on.”

“It makes styling much simpler and quicker (everything is co-located, no need to write selectors, no need to make up class names”