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.

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.

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

Sure...but the encapsulated components are still mumble jumble 😂

They're really expecting you to lean into encapsulating components as part of your JS framework. This is a familiar approach to XAML-based UI frameworks on desktop and mobile.

Building getinboxzero.com and sharemint.xyz.

I also run a YouTube channel, "Learn from Open Source": youtube.com/elie2222 

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.

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.