
Nyxarion
@nyxarion

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. 3 replies
1 recast
9 reactions
0 reply
0 recast
0 reaction
7 replies
1 recast
34 reactions
10 replies
2 recasts
46 reactions
3 replies
2 recasts
11 reactions
0 reply
0 recast
0 reaction
2 replies
7 recasts
26 reactions
0 reply
2 recasts
3 reactions
2 replies
5 recasts
25 reactions
16 replies
18 recasts
135 reactions
11 replies
15 recasts
72 reactions
0 reply
0 recast
0 reaction
3 replies
0 recast
10 reactions
5 replies
0 recast
22 reactions
3 replies
4 recasts
41 reactions
9 replies
10 recasts
68 reactions
0 reply
0 recast
0 reaction
2 replies
4 recasts
21 reactions
6 replies
9 recasts
72 reactions
85 replies
57 recasts
326 reactions