News for hackers. Stuff that matters.
Re:TailwindCSS v2.0 by citrons on Thursday November 19, 2020 @03:05AM (#25147249)
I took over a fairly large project which used tailwind v1. Have a low-hate relationship with it.

I like how fast you can do stuff, but when when a designer creates something a bit custom it all falls part really quick.

I understand it solve the issue with reusability and style-guides, but for modern apps that would also mean everything should already be react componentized, so you shoudl not really care about css at that point idealy.

I rather use a mix styled-components (easily extendable if you need something custom) and css-variables for dark mode and defining global variables like colors,paddings etc. Plus I route-split so page only has it's related styles.

Re:TailwindCSS v2.0 by corytheboyd on Thursday November 19, 2020 @04:04AM (#25147601)
Engineers of the world, push back on this stuff! Chances are your designer will want to work with you to make designs fit the tooling used to implement them. It doesn’t hurt to at least try it, ask questions. It does hurt to silently hold grudges and release what you know is suboptimal.
Re:TailwindCSS v2.0 by sbergot on Thursday November 19, 2020 @03:40AM (#25147460)
I'd say that tailwinds only works if the designer is on board or if you are not working on pixel perfect specs.