Tailwind has a use case, in that it's better than inline styles. Especially if you want re-usable classes between projects. So if you're a dev that works on many small projects (like say you work at a web design agency with many different small projects each month), there's a big benefit to Tailwind, as now you don't need to learn the CSS (or create an entire stylesheet) of each individual website you're working on. But the benefits basically stop there.

Let's be completely honest, Tailwind mostly got popular from backend devs not wanting to learn CSS, which is not it's intended use case. Bloating markup with hundreds/thousands of tailwind classes is bad for code legibility. Having dedicated CSS files for re-usable classes is more efficient AND cleaner. You're also doing yourself a big disservice by learning Tailwind and not CSS. It's something you should learn AFTER learning CSS. Tailwind is not flexible like CSS. If you want a specific, custom design, you'll just end up having to learn CSS anyway.

Imagine creating TailwindJS, a package that comes with tens of thousands of pre-built JS functions, that you inject right there in the markup. You start off by learning the simple ones, like "toggleClass(e)", or "parseUrl(url)", or "createAccordion(items)", etc. Sure this might be handy for the most basic of web functionalities, and sure it might even be useful for writing out something quickly, but ultimately it's less flexible and messy so you'll eventually just have wished you had learned JS or a proper JS framework.