i showed up to read your webpage, not a thousand lines of CSS

Follow

this is a subtoot of

people {
who: write;
their: css;
like: this!important;
it: takes;
up: so;
much: space;
and: distracts;
from: the(content);
which: "i came";
to: see;
}

· · Web · 2 · 0 · 0

@monorail i’m reading the HTML; i’d rather not read the CSS but there’s so much of it

@Lady ah

i mean i don't optimize my websites for people reading the html tbh...

@monorail yeah practically speaking if i need to grab a short fragment of HTML i do it through the web inspector (which i do sometimes, if i’m like pulling a quote from a page and want to preserve the markup they used) and it’s not a problem

i’m usually only actually looking at the full HTML of pages when i’m doing development work on them, so this complaint can be mostly ignored lmao

@Lady i mean when you’re learning it definitely makes it a lot easier to debug

@Satsuma hm i feel like an important caveat here is that the order of properties should be sensible, like

Margin: 0; Border: None; Padding: 0; Font-Family: Serif; Font-Style: Italic; Font-Weight: Bold

is fine but

Font-Family: Serif; Padding: 0; Font-Style: Italic; Border: None; Margin: 0; Font-Weight: Bold

is atrocious

i think the one‐property‐per‐line syntax encourages the latter, whereas putting it all on one line encourages people to order their properties like a sentence

Sign in to participate in the conversation
📟🐱 GlitchCat

A small, community‐oriented Mastodon‐compatible Fediverse (GlitchSoc) instance managed as a joint venture between the cat and KIBI families.