DefederateLemmyMl

Installing Linux has never been particularly difficult, not in the last 15 or even 20 years anyway. I’ve always found it easier and more straightforward than the contemporary Windows installation process.

The challenging part is wrapping your head around the Linux/Unix way of doing things when things can’t be done through the GUI with just a few clicks.

Well I’m sure it’s been in use for a while, but not in mainstream internet lingo is my point.

Speaking for myself, I only learned about this term a year or so ago, because I remember looking it up, and I remember thinking: huh, so there’s a word for that now. Since then, I’ve seen it come up several times, almost always in greentext posts like this one.

In academic circles, sure, but it’s fairly recent that it has been seeping into internet language, mostly through 4channers who started using the term for themselves in a self-deprecating way.

For me the current State of Text Rendering is that I don’t have to think about text rendering anymore. And that is awesome.

I remember the dark days of having to patch freetype and cairo with infinality patches and the endless tweaking. Nowadays you get good (enough) font rendering out of the box, and it’s rare that you have to tweak something.

How is that not enough? It’s in standard ISO8601 format and can unambiguously be reduced to a UTC timestamp, which is all that matters.

Some absolutely heartbreaking cases on there by the way, for example: https://en.wikipedia.org/wiki/Celia_(slave)

People are fucked up.

No, the first woman to be hanged by the US Federal Government.

The US had the death penalty since colonial times, so several were hanged well before 1865. This list has several examples. Most of these women were executed for ordinary crimes like murder or robbery, so not a federal offense like treason.

I know what it theoretically is for, I still think it’s a bad implementation.

1. It often doesn’t tell you clearly what it is waiting for.
2. It doesn’t allow you to checkout what’s going on with the process that isn’t responding, because logins are already disabled
3. It doesn’t allow you to cancel the wait and terminate the process anyway. 9/10 when I get it, it has been because of something stupid like a stale NFS mount or a bug in a unit file.
4. If it is actually something important, like your Redis example, it doesn’t allow you to cancel the shutdown, or to give it more time. Who’s to say that your Redis instance will be able to persist its state to disk within 90 seconds, or any arbitrary time?

Finally, I think that well written applications should be resilient to being terminated unexpectedly. If, like in your Redis example, you put data in memory without it being backed by persistent storage, you should expect to lose it. After all, power outages and crashes do happen as well.

That’s what systemd’s dreaded “a stop job is running” is

The worst part of that is that you can’t quickly login to check what it is (so maybe you can prevent it in the future?), or kill it anyway because it’s likely to be something stupid and unimportant. And if it actually was important, well… it’s gonna be shot in the head in a minute anyway, and there’s nothing you can do to prevent it, so what’s the point of delaying?

Even worse if you clicked “Update and restart”