
Sunbeamwillow
@sunbeamwillow

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. 2 replies
1 recast
8 reactions
0 reply
0 recast
0 reaction
28 replies
19 recasts
171 reactions
6 replies
7 recasts
43 reactions
0 reply
0 recast
0 reaction
2 replies
7 recasts
27 reactions
28 replies
27 recasts
301 reactions
25 replies
21 recasts
150 reactions
7 replies
6 recasts
45 reactions
0 reply
0 recast
0 reaction
29 replies
28 recasts
273 reactions
3 replies
4 recasts
41 reactions
29 replies
7 recasts
128 reactions
16 replies
20 recasts
309 reactions
0 reply
0 recast
0 reaction
13 replies
7 recasts
53 reactions
6 replies
6 recasts
75 reactions
34 replies
25 recasts
176 reactions
15 replies
20 recasts
221 reactions
0 reply
0 recast
0 reaction