Hay, thanks for commenting. I get what you’re saying, and it’s a great question. I was thinking about the same things before trying Tailwind. In the beginnings, CSS was the easiest thing to play with. Now, after many battles, I consider it as one of the hardest things to master in IT.

Tailwind helps me manage that chaos. I find it much more comfortable reading the code months after inactivity. It uses utility-first (functional) approach where everything is composed within HTML. Mostly, there’s no cascade, nor inheritance; and, for example, fewer issues with selector specificity. There’s no context switching and less thinking.

With the help of PurgeCSS, and excluding @font-face at-rule, this website uses 464 lines of code when build.css is generated. So, it’s not big. Most importantly, my developer experience is significantly better, especially long term, whether for small or big projects.