the more likely explanation seems to me that not all panels were hit by a sufficiently large hailstone to cause an initial break. once the structural integrity of a panel is broken, smaller stones can damage it further that wouldn't have otherwise..

Probably not just the size of the hail that hit it, but where the big pieces hit it. At a first guess they're using tempered glass, and that's a lot more likely to fracture if you hit it near the corners than the centre.

> Long gone are the days of 62.5% font size trick.

Isn't the 62.5% trick about making the code easier to write/understand/maintain? Or are you advocating for not using relative units at all? That might work for some use cases however it breaks if you need any kind of scaling feature within the site/app.

62.5% was specifically to bring the default 16px to 10px, which meant now 1em = 10px, at least at the root. With that, you could easily size your entire layout in EMs and, yes, keep it readable:

    .main {
        width: 80em
    }
    .sidebar {
        width: 20em;
    }
    .content {
        width: 60em;
    }

There's no point in bringing the font down to 10px if you're not going to use EMs

As far as i understand it's about `rem`, not `em` (which is relative to it's parent not the 62.5-normalized root element). And as long as you don't go all-in with absolute units (and loose all control over custom scaling on your site/app), you still need `rem`.

The 62.5 hack has been around for a decade before rem was even thought of. The fact that rem would be a better fit for it is irrelevant to the conversation.

I'm just saying that using em and rem for sizing isn't as useful as it once was.

My rule of thumb is to only use them for things directly related to text, like inline icons, text spacing and whatnot.

i'm basically running that setup: rpi, external usb, encrypted backup.

- i'd recommend attaching an external 3,5 disk that comes with its own power supply, that way you don't have to worry about power, it's cheaper and you have more storage.

- For backup i am using borgbackup. it does encryption and deduplication. you can also backup several machines to the same repository if you want to. i'm using it for several use cases, it's rock solid, never had a problem.

- you can safely use borgbackup over ssh if you want to do remote backup. just forward the ssh port on your friends router and use dyndns if they don't have a static ip.

simple @NVIDIA: threat to reduce LHR to 10% if anything else is released