3 ms·
The usual answer, however trite, is "don't knock it till you've tried it." I haven't found a convincing explanation of why exactly this is better until I've us
by sph 4y ago
The usual answer, however trite, is "don't knock it till you've tried it."
I haven't found a convincing explanation of why exactly this is better until I've used it in a project, and since then I'm completely sold. The semantic CSS concern separation pipe dream has always been snake oil in real projects.
Long live Tailwind.
- jonwinstanley 4y agoAlso - no more constant switching between the HTML and the corresponding style rules
- danielvaughn 4y agoI ended up deleting like 30% of my React components after switching to Tailwind, because suddenly they just felt like unnecessary overhead. Tailwind FTW.