Hacker News Reader

Hacker News

Comment by geek_at | Hacker News Reader

Parent Full thread

geek_at

Less verbose? Ha, far from it. Look at the tailwind examples. One div tag now has 6 or more classes attached

View on HN

Well I suppose it's less verbose than a lengthy style="..." attribute that accomplishes the same thing.

Now it's a lengthy css instead. It seems to me we are going backwards...

Out of interest, have you built anything non-trivial with tailwind?

I've used CSS, and Tailwind and not worrying about naming everything correctly and not skipping around different files is a dream for me. Perhaps that's my brain, Idk.

Further I have gone over old code, and haven't had any problem with maintainability

> Well I suppose it's less verbose than a lengthy style="..." attribute that accomplishes the same thing.

It's not actually the same thing. What you're talking about is inline styling which takes precedence over class-based styling. It's generally considered bad practice to rely on inline styles. The traditional approach is `style="card"` not `style="...a bunch of rules..."`

  <div class="block text-black">...</div>
  <div style="display: block; color: black;">...</div>

Looks like the same thing to me. Only shorter.

With traditional css you'd most likely have a class for all the relevant attributes.

Of course. That's how I learned CSS and how I wrote the CSS for my site. Apparently that's not how things are done these days. People have one class for every property and value combination now and essentially write the entire class inside the class="..." attribute. Can't understand why.

Like I said. It's not at all the same thing. Inline styles have different behavior from class-based styling

Reply on news.ycombinator.com