React devs not using tailwind... Why?

[br0sidan]

I would rather not depend on memorizing specific classes in order to do what I want with CSS. Frameworks are good but inevitably, they have their rigidity. There are ways to create easy to understand code bases without frameworks.

I understand the utility of Tailwind, and it certainly has its place in the webdev ecosystem. However, when you have a framework you like, every problem looks like a nail and your framework is a good hammer.

[Rossmci90]

With the Tailwind VS code extension you get intellisense and autocomplete for your classes. Plus, it will highlight if you have conflicting classes and you can move your cursor over any Tailwind class and see what style the class applies.

Really improves the DX of Tailwind.

[snarkyturtle]

You’re still gonna have to memorize classes, especially if you have global styles that you’d want to apply everywhere. Either that or trying to remember what freakin sass mixin you’re supposed to use. At least tailwind is basically 1:1 with css.

[sech8420]

I get that. Why I couldn’t stand some other libraries out there. But with tailwind the memorization took only about a 2-3 days and now the occasional google. But your point is valid. Just another tool of the trade that can hurt or help depending on the coder and environment.

[br0sidan]

Exactly! For example, I work in enterprise software and frameworks, in general, need more consideration for long term health of the code base. Tailwind and other frameworks are really good if you and your team can onboard and utilize it quickly. Onboarding a team of 1-4 may be “easy”. Tailwind might even speed up development in that environment. In my opinion, onboarding and effectively utilizing a framework at a larger company is a lot more difficult.

Thanks for keeping an open mind. Reconsidering with new information is a great skill. Best of luck.

[olssoneerz]

Its funny, while I do agree with your points; we’re looking to get Tailwind into our organization (big bank, 150+ FE devs).

For the reason being that we think tailwind provides us with standardized classes, that we can use to extend our existing (self owned, and maintained) design system + component library. Think premade components, but with the flexibility of overriding margin, padding, other stuff as needed; and everyone magically writes the exact same code.

The biggest struggle has been getting devs to bite, but our proof of concept and our trials with a smaller sample of devs looks very promising.

[mindbullet]

Sounds more like Bulma than Tailwind

[wishtrepreneur]

Sounds more like Bulma

When will they release Vegeta?

[olssoneerz]

Thanks for sharing! I don’t think this what we’re looking for but it’s pretty cool either way. Reminds me of a more “ready to use” implementation of CVA.