I love tailwind too. The article did not convince me as there was also no real solution / alternative proposed. I have written custom css since the year 2000 a

I love tailwind too. The article did not convince me as there was also no real solution / alternative proposed. I have written custom css since the year 2000 and using tailwind just makes me much faster (is like setting flags) and simply by reading it, I understand how an element looks like. No matter if my past-self wrote it or another engineer. It can pollute the HTML (although @apply helps a lot to define your reusable .title, .card, .btn, .btn-lg, .btn-primary etc), but at least it is written in HTML and not in JS, which is even harder to transfer to other eco-systems. Also extending styles (tailwind config) is amazing if you want to reuse your styles in other projects.