> since there's no way to eject, you're more willing to justify it to yourself as worth it
You honestly have no idea what you're talking about, and you're making that very clear.
Lots of people in this thread have used tailwind as well as many other CSS maintenance strategies, and almost all of us prefer tailwind.
Not that mass approval makes it "right", but you certainly can spend 3 days writing your next greenfield project with tailwind, and then if you want to "eject", it would take all of 20 minutes
> You honestly have no idea what you're talking about, and you're making that very clear.
Rudeness aside, I made it very clear from the beginning that I haven't tried Tailwind, and my criticisms were based on fundamental principles that could apply to any new tech.
Of course I don't know what I'm talking about when it comes to tailwind - I've never tried it. I hoped my points could be read as constructive criticism as to how to convince someone to try it, rather than an invitation for the cult-of-tailwind to pile on with insults and appeals to authority of influencers pushing foot-in-the-door sales tactics. It doesn't exactly instill a lot of motivation to join the ecosystem, and it only proves my point about the culty vibes around it.
Fair response. If you don't know what you're talking about, why are you making assertions that are incorrect, rather than asking "what's the process for ejecting if I try tailwind and don't like it?"
You just freeze the minimal CSS file generated by Tailwind (it tree-shakes out any class selectors for tailwind classes you're not using) and remove all tailwind dependencies; you don't have to make any more changes to your code, you're just left with the classes you've already added to your markup, which still work. You can gradually change those out however you want, at your own pace.
Also, using tailwind doesn't mean you can't use CSS the way you're used to in addition to the tailwind classes, though it's possible you could end up with specificity issues if, for example, you've added a tag selector, like `div {...}` which is overridden by a class you've added to a specific div in your markup. This is pretty straightforward though, and if you've been using CSS for any amount of time you'll still find you have to think a lot less about specificity than going all-in on your own CSS
You honestly have no idea what you're talking about, and you're making that very clear.
Lots of people in this thread have used tailwind as well as many other CSS maintenance strategies, and almost all of us prefer tailwind.
Not that mass approval makes it "right", but you certainly can spend 3 days writing your next greenfield project with tailwind, and then if you want to "eject", it would take all of 20 minutes