A place for developers to talk about building on Farcaster.

/dev

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.

Could you define "terribly unreadable code"? Curious to hear what you're comparing it to and where the tailwind approach fails.

I moai you moai we all /moai / prev: sloika.xyz / contributing to @kiwi as kiwinews.lol

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.

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.

That looks more XAMLish than I anticipated, I approve.

"flex justify-content bg-red-500" is really easy to read.