“I don’t need Tailwind
“I don’t need Tailwind. I’m a CSS expert.”
⚠️Will your docs will be as comprehensive?
⚠️Will your class structure will be as thoughtful?
⚠️Will your dev tools and extensions be as robust?
⚠️Will your build automatically exclude unused styles?
⚠️Will new hires potentially already have experience with your approach?
⚠️Does your entire dev team have a shared understanding of your CSS strategy?
The answer to these questions is almost certainly "No."
So, the most likely outcome of not using Tailwind...is creating an inferior alternative to Tailwind.
More things that are hard to get right in plain CSS:
⚠️ Will your solution provide autocomplete support for class names?
⚠️ Will your solution support hovering class names to see the styles they apply?
⚠️ Will your solution avoid scoping issues?
⚠️ Will your solution support theming?
⚠️ Will your solution assure we don’t repeat styles?
⚠️ Can I safely delete a style and know it won’t break other spots?
These are handled by Tailwind.