“I don’t understand Tailwind. The entire point of CSS is to separate style from structure. How does applying composable utility classes differ from the old days of using HTML attributes for styling?”
“This is essentially the same as inlining all of your styles in a style attribute on every element. I don’t see how you would ever reasonably want to use this in a project.”
“Wasn’t the whole point of CSS to separate presentation from data, and move away from things like <font color=...>? This is still considered bad practice, right?”
“I don’t get it either. Start putting CSS in the style attribute while you’re at it.”
“The emperor has no clothes.”
The exact same ‘separation of concerns’ argument was levelled against React in 2013. HN missed it twice.
What happened
Tailwind CSS became the most-downloaded CSS framework in the world with 100M+ npm downloads per month. It’s now the default styling choice for millions of developers, used by Shopify, OpenAI, Netflix, and GitHub itself.