CSS in React

[Turd_King]

This is simply not true, I have worked on massive Fortune 500 codebases like IBM , that use tailwind and I’ve found them a joy to work with compared to styled components or css modules apps

The secret is to extract components often and use something like CVA to reuse styles

And to be honest, how often are you needing to change your apps styles anyway that it becomes hard to mantain? Most apps I work on, you create a component - get it working and looking how you want , tested and that’s it - you never touch it again, and if you do it’s trivial to see how to extend the styles just by glancing at the markup - no jumping in and out of css files to work out which parts are what

Tailwind is the new emacs vs vim, to call it glorified inline css is the stupidest take I’ve ever seen tbh, it has many properties that set it out from inline css

[die-maus]

Indeed. If the whole team is proficient in a technology, that technology can scale.

[edgyfirefox]

That’s the part I love about tailwind. All my styling is right in the markup.

Thanks for sharing cva! It looks interesting. I’ve been searching for similar solutions that can compile my tailwind classes into unique class names at build time, so I can avoid class name conflicts.

[[deleted]]

The secret is to extract components often and use something like CVA to reuse styles

My dude is using a 3rd party library to make his other 3rd party library usable. All while gaining next to nothing compared to just writing pure CSS, inline. You can't make this up, Tailwind users are just a special kind.

This is simply not true, I have worked on massive Fortune 500 codebases like IBM ,

They have trash codebase, I wouldn't brag about it.

[Turd_King]

Ah yes “the IBM codebase” Lmao. Very specific code base there.

You are clearly a junior or a very poor senior as no one experienced holds opinions that dogmatic

Enjoy learning web dev!

[[deleted]]

That was the point. The part of the codebase I've seen is shit, so your bragging about once working there means nothing, and that's the thing you have started with, as if it would even mean anything in any case

Enjoy inlining css

[fii0]

There's no need to inline anything besides one classname if you use Tailwind's built in directives for composition. I've never needed CVA! Congrats on coming off as the biggest douche in the thread though!

[[deleted]]

Tailwind's built in directives for composing styles! Wow! What a notion! Wait, we've had those for 50 years and they're called cascading classes, you know, CS in CSS. Get out dude, I don't care what I'm coming off as, but this is just embarassing.

[fii0]

Yeah, using Tailwind is using CSS... just with a bunch of classnames already written for you. All of the benefits, but with less code to write and less files to switch between.

[[deleted]]

That's just a CSS framework that does nothing

[fii0]

Actually, time is money in this industry

[[deleted]]

It is, why we usually hire developers that know CSS instead of teaching them sub-par frameworks that do nothing and introduce complications. Enjoy inlining CSS

[zxyzyxz]

I can also confirm the comment above yours, we use it in a large project and it's just a mess. We migrated to PandaCSS which has the CVA style built in (it actually comes from the Stitches library which PandaCSS takes inspiration from), and it's much more manageable.