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
freeatnet ๐ฟ๐ฉ
@freeatnet.eth
Could you define "terribly unreadable code"? Curious to hear what you're comparing it to and where the tailwind approach fails.
1 reply
0 recast
1 reaction
Volky
@volky.eth
Ok, "terribly unreadable" was an overstatement. Utility classes are difficult to reason about. You can't glimpse the code and instantly figure it out. class names pile up fast. Personally, I enjoy the Chakra-UI approach with style props. It's much more expressive, and you have more control with conditional styling.
3 replies
0 recast
2 reactions
Volky
@volky.eth
I'm well aware they are completely different beasts with different use cases, and code portability matters. Just think people shill Tailwind as a hell yeah solution, but I don't get it.
1 reply
0 recast
0 reaction
freeatnet ๐ฟ๐ฉ
@freeatnet.eth
I think that's a fair assessment! If it were so easy to read/write, IntelliSense and class sorting prettier integrations wouldn't be as popular.
1 reply
0 recast
1 reaction
freeatnet ๐ฟ๐ฉ
@freeatnet.eth
Fwiw, I've never seen people _shill_ Tailwind. I think it's better than writing CSS files/modules at scale, but the React Native component styling approach is still my favorite.
1 reply
0 recast
1 reaction
