Secondly though, and why this opinion is frankly stupid, is that I can just put this in my CSS code before it’s built through Vite:
input { @apply bg-white focus:outline-none focus:shadow-outline border border-gray-300 rounded-lg py-2 px-4 block w-full appearance-none leading-normal; }
And then lo and behold, I’ll do you one better:
<input type=“text”> </input> is now fully styled, with Tailwind only.
Strange you would be worried about accidental overrides with class selectors but then go ahead to target styles with tag selectors. Is that not objectively worse?
Btw, targeting input[type=”text”] means now you cannot apply those styles to a regular <span> or <div> using a class, which is sometimes useful, especially in very large projects.
I am still not at all convinced Tailwind is even slightly useful.
All in all, your arguments come off as ad hoc rationalizations for a personal preference, not as substantial examples of Tailwind’s superiority over more traditional CSS approaches.
I think it’s much easier to understand what
is supposed to be compared to