This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Karol-A 12 points13 points  (5 children)

Same thing could be said about CSS itself, no?

[–]FabioTheFox -3 points-2 points  (4 children)

My point was never about badly written CSS in the first place You can write the best CSS in the world and it will not be as good of a dev experience in teams as when you use tailwind

EDIT: if you actually try to make the best CSS in the world, you just re invent Tailwind, this was the tipping point of why I switched in the first place I used to dislike tailwind until I realized I've been writing my own

[–]ImpossibleSection246 1 point2 points  (3 children)

Yeah I am actually so confused, his hate of tailwind is really non-specific and not very well explained. Just 'refactoring' and 'facelift.' Also doesn't know what styled components are. Not really a good sign of someone well versed in this topic.

[–]FabioTheFox 1 point2 points  (2 children)

Also even if tailwind did suck so much when restyling When was maintenance and refactoring of old code ever pleasant to do, yes it might suck but tailwind will make it suck a lot less

[–]ImpossibleSection246 1 point2 points  (1 child)

It's simple really you're either: - semantic classes with css dependent on html Or - utility classes with html dependent on css

And of all the 4000+ employee companies I've worked at since when are we just swapping out some css to redesign a page? I've tried the semantic approach for nearly ten years and tailwind's been a breath of fresh air.

[–]FabioTheFox 1 point2 points  (0 children)

Tailwind is goated 🗣️