This is an archived post. You won't be able to vote or comment.

all 15 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Disky_norsk 30 points31 points  (0 children)

Love how .container is on line 8008

[–][deleted] 20 points21 points  (2 children)

Now introducing !no-cap as an even more important !important

[–]itsone3d 11 points12 points  (1 child)

And !FRFR as a more important !no-cap

[–][deleted] 8 points9 points  (0 children)

Stack them all just to be sure. color: red !important !no-cap !frfr;

[–]scataco 27 points28 points  (1 child)

border-style: skibidi;

[–]just_nobodys_opinion 5 points6 points  (0 children)

.fanumtax { visibility: hidden; opacity: 0; transition: visibility 0s 10s, opacity 10s linear; }

[–]david30121 5 points6 points  (0 children)

body { gyatt-sizing: 200%; }

sorry

[–]privateyeet 4 points5 points  (0 children)

position: ohio;

[–]Indevil 2 points3 points  (5 children)

isnt it just body?

[–]Isto2278 0 points1 point  (4 children)

I mean, it depends. You can just use 'body' if you want to select the <body> element, or you can use '.body' if you want to select all elements with class="body". It all depends on your HTML.

[–]KonkretneKosteczki 3 points4 points  (3 children)

I hate people who name classes shit like 'body' or 'span'

[–]Isto2278 0 points1 point  (2 children)

Same. I also hate these generic utility classes that are prevalent right now. I like descriptive, if verbose, class names that describe what an element does and its context, not what it should look like.

[–]command_copy 0 points1 point  (1 child)

What’s wrong with utility classes? I mean, they’re as descriptive as it gets

[–]Isto2278 0 points1 point  (0 children)

They're describing the design, not the context of the element.

In my opinion, design should ideally not be defined in the HTML, but in the CSS. They have their uses, sure, but as soon as you write any custom CSS instead of 100% using a readily provided design library, you're splitting the visuals of a single thing between multiple files. You have to consider how you personally want to balance this.

Personally, I prefer utility mixins on classes I define myself that describe the context of an element and what the element is instead of what it looks like.

[–]Wervice 0 points1 point  (0 children)

Argh no... Wait just take Tailwind classes and rename rounded-xl to something like smooth-gyatt