Tailwind is the worst form of CSS, except for all the others | Mux

**Third**, Tailwind encourages you to configure a limited number of design tokens. “Design tokens” is a scary way of saying: when you tell Tailwind you prefer your text size to be either 1rem, 1.2rem, 1.5rem, or 2rem, then your team can *only* use those text sizes; no 1.4rem or 16px nonsense, here. When you tell Tailwind your brand colors, your team can *only* use those colors. … Also, why do I have to learn all-new syntax for CSS I already know? Why do I have to know that it’s items-center when I already know align-items: center? And my *team* has to learn it too? Now there’s a learning curve that everyone has to climb. And it’s steeper than other tools which just express their styles in basic CSS. Not to mention, there’s the sometimes-dramatic cost of migrating from one syntax to another. That’s a big^2^ deal. And finally, what a bummer it is to add another build tool. There’s no way to just toss up an directory with some files or a client-side codesandbox without building that CSS first. And how do I add Tailwind to my SvelteKit build pipeline, again? I’ve been working professionally with Tailwind for years now. And I’m *still* not over these things. And, like with any opinionated tool, everyone’s going to have a list just like this.