I'll take Tailwind over styled-components any day, fight me

Idk maybe it's just me but after 3 months of using styled-components on a client project in Austin, I switched everything over to Tailwind halfway through. Everyone on the team said utility classes would make things messy, but I was spending way too long naming component wrappers and chasing down nested styles. Tailwind let me ship the final 40 components in like a week and a half instead of guessing where a style was coming from. Has anyone else gone against the grain on this and ended up happier?

2 comments

2 Comments

betty_fisher52d ago

Dude I used to be the biggest Tailwind hater. I was all "separation of concerns" and "this is just inline styles with extra steps" for like a year. But then I had to jump onto a project that was already using it and I couldn't stand it for the first week. Something clicked though once I stopped fighting it. Now I totally get it, the speed is insane and I honestly miss it when I go back to regular CSS.

amy_reed792d ago

Tbh naming a styled component "StyledButtonWrapper" at 2am after a 12 hour sprint makes me question all my life choices. I switched a personal project to Tailwind halfway through and it felt like cheating - no more hunting through 3 different files to change a padding value. I still catch myself writing "display: flex" in my sleep but the speed trade off is wild. I'd rather look at a bloated className string than another 800 line styles file any day of the week.