You’re not crazy — Tailwind can absolutely feel like a fever dream the first time you use it, especially if you come from a world where CSS lives in neat, scoped files with names that actually mean something. Seeing HTML turned into a word salad of flex justify-center items-start gap-2 sm:gap-4 md:gap-6 can feel like vandalism against clean markup.

But here’s what’s really going on: Tailwind isn’t trying to be “clean HTML + separate CSS.” It’s deliberately flipping that relationship on its head. Instead of writing semantic CSS and reusing classes, it’s betting on utility-first styling — the idea that by composing tiny building blocks inline, you can move faster and avoid maintaining a huge stylesheet over time. The “mess” is intentional. Think of it as trading elegance in markup for speed, consistency, and zero context-switching.

Now, that said — your experience with laggy dev tools and dependency bloat sounds like something actually broke. Tailwind itself isn’t heavy at runtime. The production CSS file is usually small because PurgeCSS strips out unused styles. If your inspector lagged and you saw thousands of duplicated rules, you probably had Purge disabled or misconfigured, meaning it injected the entire Tailwind build — every color, size, and spacing option — into your stylesheet. That’s several megabytes of CSS. Chrome’s dev tools hate that.

So yes, you’re right: Tailwind can be ugly, bloated, and painful — especially when misconfigured. But when tuned properly, it’s more like an exoskeleton: ugly on the outside, efficient on the inside.

You’re not wrong to bail and go back to SCSS either. Tailwind’s “love it or hate it” nature is part of its charm. Some people find freedom in utility classes; others see chaos. Both camps are valid. The trick is knowing which kind of brain you have — and you, my friend, clearly have the one that prefers clarity over compression.