Content
@
0 reply
0 recast
0 reaction
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
22 reactions
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
alex
@alexgrover.eth
my gripe with TW is the mental translation required for things I already know how to do in CSS. Been using it for over a year and I still need to keep the docs site open for anything more complicated than flex layout. I use it at work because of shadcn but only grudgingly
2 replies
0 recast
1 reaction
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
Royal
@royalaid.eth
tailwind is an annoying learning curve, and has some quirks around how it works with CSS grid and grouping, but overall I completely agree. Tailwind is the best way to quickly ship RN IMO
1 reply
0 recast
0 reaction
