Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
Volky
@volky.eth
I can't seem to be convinced by proponents of Tailwind. Sure, it's easier to maintain CSS with the utility-first approach, but it makes for terribly unreadable code. Trading off readability for writeability is a hard sell. You read orders of magnitude more code than you write it.
3 replies
0 recast
1 reaction
Elie
@elie
You don't need to be convinced. You just need to use it. Felt weird to me at first too, but Tailwind is way more readable than CSS/classes. Because it's in one file. Show a modern dev a React/Tailwind file and they can read it. And don't have to jump through multiple files to understand what's happening.
2 replies
0 recast
0 reaction
Elie
@elie
This is Warpcast. I can read it. If you use Tailwind you can too. That's really nice.
1 reply
0 recast
0 reaction
Volky
@volky.eth
Sure, having styles colocated with the component is a huge win. CSS in js affords that with improved readability. Check panda CSS and Chakra UI I'm not saying tailwind makes code absolutely unreadable...but it's not easy to browse through. You don't glimpse the code and immediately find what you're looking for.
1 reply
0 recast
0 reaction