this post was submitted on 30 Jun 2025
400 points (98.1% liked)

Programmer Humor

24709 readers
326 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] scott@lemmy.org 2 points 3 days ago (3 children)

At first it seems nice...I played with it for a few hours in an established project and didn't mind. But the I thought about using it from scratch and I'm just baffled anyone does. It's like if CSS was slightly more abbreviated but you couldn't use classes so every style has to be specified on every component.

[–] beeb@lemmy.zip 5 points 3 days ago* (last edited 3 days ago) (2 children)

A lot of ui frameworks are based on tailwind and allow you to customize the components with more tailwind. It's really a win because:

  • it's not "just inline classes", it's a design system (spacing, colors, breakpoints etc are well structured and not random)
  • it is way less verbose than vanilla css and easier to remember
[–] scott@lemmy.org 2 points 3 days ago (2 children)

Fair enough. What ui framework(s?) on tailwind do you like?

[–] brian@programming.dev 2 points 3 days ago (1 children)

shadcn is the primary one for react at least. they've done a great job filling the space where you're trying to build up a design system but don't want to start from scratch, but they're great if you just want prebuilt components too

all the components build on something else like radix, and are pretty simple themselves. normally just the radix component with styles. Installing a component just copypastes the source into your project at configured locations.

if you've ever fought against something like mui to get it to fit design changes or change specific behavior, shadcn is great. at some point the extension points of a library aren't enough, but if you own all the code that'll never be a problem.

[–] dubbel@discuss.tchncs.de 2 points 3 days ago

I don't use react, but needed a decently looking frontend complement library that didn't look dated, and found basecoat, which is shadcn but without react to be really neat.

Might be interesting for the htmx crowd here.

[–] beeb@lemmy.zip 0 points 2 days ago (1 children)

I like daisyUI because it doesn't have any Javascript

[–] scott@lemmy.org 1 points 2 days ago

Oooh, that's nice. I might switch to that from bulma, it would reduce the packaged style size

[–] MonkderVierte@lemmy.zip -1 points 3 days ago

Oh wow, a framework that needs a framework.

[–] Venator@lemmy.nz 4 points 3 days ago (1 children)

You can still use classes if you want to...

[–] scott@lemmy.org 4 points 3 days ago

Yes but it's also expressly discouraged in the documentation so...

[–] brian@programming.dev 1 points 3 days ago

instead of using classes you just use whatever your ui library provides for reuse. stick a classname string in a variable and you have a class. use a component and it just contains all its styles.

unless you mean that if you look in the inspector you see a mess of classnames. I don't have a solution there