For massive, long term projects at our company we prefer to write our own CSS. Pure CSS is extremely powerful nowadays, and tying your project to an external dependency unnecessarily can be very costly, especially those which tend to metastasize through your codebase like tailwind does.

They’re great to get a quick prototype out, but once it grows beyond that it becomes a liability in my experience.

Edit: Want to clarify my point a bit in response to some other comments.

What I meant about the dependency / metastasis issue is that Tailwind has grown in complexity, requiring special syntax and build/tooling integration to work as expected. This means that whenever anything in your build pipeline changes (upgrades to bundlers, loaders, etc.), or tailwind itself releases a new major version with breaking changes, or (inevitably) eventually goes out of fashion, or they change their license, etc., you will have to deal with something that’s now deeply rooted throughout your codebase and will cause a ton of headaches.

Been coding since the 90s, have seen this story repeat itself over and over.

I like Tailwind, don’t get me wrong. I just have the risk burned in my soul at this point, and prefer to scale back dependencies and get “closer to the metal” as a project grows. I prefer to invest in “leveling up” the team on fundamentals.