Post

Tailwind really shines in many agency use cases where projects are short, the codebase is not huge, and the tech stack might change between projects.Most CSS-in-JS solutions are not very portable.

From a utilities perspective, it's great. Margin here, some text formatting here. But for everything, it becomes a HTML spaghetti nightmare. I also find myself looking through the documentation for a utility class when I already know the CSS rule I want. I much prefer component-based CSS rules.

I think it depends on front-end skill level of your team and where priorities lie for your app. If team is mostly backend devs just trying to ship and iterate, Tailwind all the way (that's a lot of teams). If your team is deeper front-end and has the time/space to do things better, vanilla-extract!

I maintain and elected this hill to die on that utility classes are a great compile target. Not a great way to write styles.

I’m increasingly sold on it too.