Content pfp
Content
@
0 reply
0 recast
0 reaction

df pfp
df
@df
One thing I changed my mind about in 2023 is tailwind CSS. I started the year curious, but not convinced. Now I can't imagine working without it - particularly with shadcn. Over the last 10 years I've gone thru: global CSS -> SASS -> BEM -> PostCSS -> CSS in JS -> CSS Modules -> Inline styles (fuck it) -> Tailwind
4 replies
0 recast
21 reactions

df pfp
df
@df
tailwind gives you the best of inline styles: - code colocated by relatedness, not by language or part of stack - no mental overhead/naming/referencing - no jumping between files - copy pastable But with improvements: - standardized values & systems - more concise - bundling & optimization - lib composability
3 replies
0 recast
3 reactions

GIGAMΞSH pfp
GIGAMΞSH
@gigamesh
I've been using Stitches and really like it. I've also used tailwind and liked it, but don't like having to use a different syntax and how messy it makes html. Do you recommend I switch?
1 reply
0 recast
0 reaction

df pfp
df
@df
more than 8 tailwind classes on an element and it should probably be component(s) instead. Css in JS is dying; stitches is no longer maintained. Would recommend https://ui.shadcn.com/ which uses tailwind under the hood
1 reply
0 recast
0 reaction