Lady @Lady@cat.family

plus a filesystem path is a much more human-friendly identifier than a UUID but this is the URL thing again

anyway the idea that Zoomers will replace the tree directory structure is kind of hilar; i don't think the author realizes that people have been trying to replace the tree directory structure for a half-century and the reason they haven't done it yet is that it's really fucking hard

if a tree structure is important for your data you can easily handle the problem by wrapping the data in a container and only showing the container to the user. probably a better solution anyway because it means that the computer can enforce good structure at the container boundary. who cares

however, there is one other domain where the concept of a “path” is relevant, other than the filesystem… and it’s kind of important…

“kids these days don’t understand tree directory structures” i sleep

“that means they don’t understand URLs” i weep

will they let me play this with the N64 controller they announced

got THPS on switch because it's on sale and completing all the challenges except “score lots of points” because <del>i can’t</del><ins>that’s how i play Tony Hawk</ins>

today’s issue is “if the scrollbar is on the left instead of the right (because of a right‐to‐left directionality) and the background of the element changes, safari won’t repaint the part of the element underneath where the scrollbar would have been on the right‐hand side”

a lot of safari’s painting operations assume a left‐to‐right top‐to‐bottom writing mode and simply fail to paint the correct part of the viewport if it isn’t that

gdi safari stop having bugs with writing modes check your dang software

@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

@Satsuma does it? i find it much less readable

@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

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

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;
}