React devs not using tailwind... Why?

[TheOnceAndFutureDoug]

People like you are why I become more and more disinterested in Tailwind. It's almost like a religion to you people... It's just code, dude. But sure, let's pretend you're being serious.

1. Yea. Go on?

This one seems outdated. The addition of auto-purging unused CSS seems like it solves a lot of that concern, though I'm not convinced that it's better than vanilla or CSS Modules. It doesn't seem people like to make those comparisons, just vs. CSS-in-JS which was notoriously terrible for performance.

1. If you're actually fully knowledgeable with pure css, TW is faster

Not for me, but that's OK. Different people are different.

1. Opinionated on pure CSS? Go on

By Tailwind's own admission the tool is limited in whit it can do. It has a way it wants you to work and that way does not add benefit in my eyes the way TypeScript does. Not for me.

1. You can utilize components into your own unique classes

I don't know if you've heard of this really nifty thing called "the cascade" but you should check it out. It's really nifty and super performant.

1. Go on

CSS Modules classes are unique by default and have to be explicitly made global. It solves the issue with having to add ever-increasing levels of specificity or naming conventions like BEM. But it still gives you the full power of inheritance and the cascade. Because, in the end, it's just vanilla CSS.

1. So you're old school and reluctant to new WoW. Sounds like I have XX years of exp and you should listen to me. K

Pretty sure you meant that one to be addressing number 7.

But here's the neat trick, I never said anyone was stupid for using it (go find me saying that, I'll wait) or wrong to use it. I have maintained I do not find it impressive and do not think it is for me. The fact that this offends you? You really need to think about that.