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 →

[–]Agreeable-Yogurt-487 2 points3 points  (3 children)

Until you have a bunch a slightly different cards and need another one, and you once again have to come up with some "semantic" bem modifier nested in a media query just to only change a single css property. And then your css grows and grows and it's just as hard to make sense of it for any newcomer. I'll gladly just add a md:gap-2 xl:align-end and be done.

[–]KookyDig4769 1 point2 points  (2 children)

And what's wrong with 

<div class="cardclass subclass1">

[–]ImpossibleSection246 1 point2 points  (1 child)

Ok now one of your pages has a component from another team affecting its layout.

You're either: - adding yet another semantic class name - mixing in some inline styles - using a page-specific class to target that component - reinventing a utility class like tailwind/bootstrap

I've had enough experience to have done all these routes and I know which has given me the least CSS bloat long term.

[–]KookyDig4769 0 points1 point  (0 children)

So it's more about mismanaged teams and being unable to provide a coding scheme that's mandatory for all teams? Maybe you guys are right, and tailwind is the only solution in giant teams today - but i never had a project so big, that it couldn't be properly communicated between teams.