Complaints about TailwindCSS always remind me of this quote:
“It is difficult to get a man to understand something, when his salary depends on his not understanding it.”
― Upton Sinclair, I, Candidate for Governor
Tailwind (and similar, I tend to use https://unocss.dev/) is not good for your frontend architecture BUT they allow you to be so fast, that it negates the benefits.
For a job well done, I'd follow the principles of https://maintainablecss.com/
For throwaway code I need to cram out as fast as I can, Tailwind it is.
I understand agencies using Tailwind, or Bootstrap, their revenue depends on it.
What's the definition of a job well done? In my eyes it's completing the project and getting it out the door to customers to use. If Tailwind makes that happen, then isn't it a job well done?
> Built by experts — you can trust that all of the code is written following Tailwind CSS best practices, because it’s written by the same team who created and maintain the framework.
Tailwind (and similar, I tend to use https://unocss.dev/) is not good for your frontend architecture BUT they allow you to be so fast, that it negates the benefits.
For a job well done, I'd follow the principles of https://maintainablecss.com/ For throwaway code I need to cram out as fast as I can, Tailwind it is.
I understand agencies using Tailwind, or Bootstrap, their revenue depends on it.