A lot of Tailwind's value comes not from the utility classes, but from the design system they enforce on the user, which is the most valued feature Tailwind offers, in my opinion.
I have been using 3.5 sonnet to generate me tailwind components it does a pretty good job, and then with clsx, tailwind-merge and tailwind-variants things become pretty maintainable. I reach-out to shadcn-svelte when I need components which would take some extra tuning.
Aside from the Tailwind discussion: The site advertises FREE templates, I select a FREE template, but when I want to use it, I STILL have to pay. Huh?<p><a href="https://tailwindtemplates.co/templates/basic" rel="nofollow">https://tailwindtemplates.co/templates/basic</a>
Tailkits offers a lot of website templates that are written in tailwind, which are great to use when developing front-end pages, and even the free templates look great!
I really was hoping that tailwind was a fad which died but like everything JavaScript it's here to stay sadly<p>I recently found myself staring at a button element with more classes than I have ever seen like <button class="bg-blue-500 hover:bg-blue-600 text-white font-bold py-2 px-4 rounded-md shadow-md">Click me!</button>.<p>It’s like the eccentric artist who insists on using every color in the palette. After been forced to use it for almost 2 years I still don't see the point. Your HTML files? Bloated. Your sanity? Questionable. And those cryptic class names? Why God did we have to do this.