TailwindCSS will eventually fail if something doesn’t change

I’ve been a TailwindCSS user since day one. It was a hard no at first (as it still is for most people), but I gave it a try anyway because it was something built by Adam Wathan. It just goes to show how valuable is the trust you are building with your audience.

As soon as I learned most of the utility classes, I was flying. Everything was getting built much, much faster than ever before. It was incredible.

From time to time, I would feel disgusted by the never-ending list of class names in my templates, but heh, fast was fast. As time passed, though, I grew more annoyed with the way my templates look. I couldn’t take it anymore. I tried using the @apply directive to clean up things a bit. It felt better, refreshing.

I’m pretty sure @apply was added just to shun the naysayers. It’s not really a solution. Neither is extracting template components. All the speed I gained using TailwindCSS was thrown away at fiddling with the @apply directive and extracting components.

We need something that will keep or slightly reduce the speed of TailwindCSS but will massively clean up our templates. That could be anything from a change in how TailwindCSS works to a plugin where you can select and extract a bunch of classes with a keyboard shortcut.

Most people are still under the “heh, ugly, but I’m moving fast” spell – so there’s plenty of time to make TailwindCSS better.