0 reply
0 recast
0 reaction

Tailwind continues to be the bane of my existence. If youâre building a UI library, potential conflicts with the consumer are death by a thousand paper cuts. Yes you can prefix but the cost is getting everybody (including AI) to adopt your different class names. AI hates deviating from the norm and tbh so do I (my prettier.rc is always {}).
âBut if youâre not building a library, itâs so much faster!â Maybe, depends on what youâre building and how well you know CSS. If you donât wanna learn CSS, sure, but the spec keeps expanding and Tailwind has to keep up.
My biggest issue with Tailwind in non-library projects is that, in my experience, it makes people not make UI components. Your button styles, for example, are duplicated everywhere. Need to tweak a border radius? Cool, you have to update every button cause thereâs no canonical styled button component.
Is that an inherent issue? No, but if you give people the choice to be lazy, they will be lazy. Is it a problem specific to Tailwind? No, but itâs so common in Tailwind codebases.
CSS modules all day. Sorry. 4 replies
2 recasts
9 reactions
1 reply
0 recast
0 reaction
0 reply
0 recast
1 reaction