That's the opposite of how that works. It's LGPL 2 or later. That means you can follow the terms of redistribution from either license. Either. Or.

It will do the same jobs. Most of the software on which we depend predates the GPL3 and/or uses an even more permissive license without an anti-tivoization clause.

Was it the monopoly that made the difference? Or was it simply management smart enough to not only not kill the goose, but also to feed it? They had wins, they got more funding, they had more wins, repeat until they no longer got more funding and stopped getting wins. What's probably more important than why they succeeded is what happened at the end.

If you're a Debian derivative user, it's called Devuan.

Otherwise...*

* Note: Removing systemd from a systemd-based system is madness. There's a reason Devuan exists, and it is that simply changing the init system on Debian results in a lot of breakage, which best illustrates the biggest problem with systemd.

Yes, that is literally the entire ethos behind systemd.

Yes, that is literally the entire situation with systemd.

This change literally could not be more on brand for systemd.

That's systemd in a nutshell. Only people like that would willingly work on a project like that.

The Linux kernel is GPL2 and glibc is LGPL, and you can construct a complete userland without any GPL3 components. Also, you seem to be under some weird misapprehension that the federal government will follow the law, which it has never done across the board.

Amendment XIII
Section 1: "Neither slavery nor involuntary servitude, except as a punishment for crime whereof the party shall have been duly convicted, shall exist within the United States, or any place subject to their jurisdiction".
Section 2: "Congress shall have power to enforce this article by appropriate legislation".

Emphasis mine.

Collaborators can get it.

Everyone is doing it wrong, that's why we need to sandbox.

Even if you were perfect, you wouldn't have time to do everything yourself, so you would still want sandboxing to protect you from the efforts of others.

I’d argue that slavery wasn’t “legal because nobody banned it.” It was legal because there were explicit laws that created, defined, and enforced the institution.

There were statutes specifying who could be held as slaves, rules that the child of an enslaved woman was automatically a slave, procedures for manumission, regulations on how slaves could be bought, sold, punished, or inherited, and laws requiring that escaped slaves be returned. That’s not a legal vacuum, that’s a full legal framework.

It’s similar to how segregation laws later forced discrimination on people who might not have engaged in it otherwise. The state wasn’t passively allowing something; it was actively mandating and structuring it.

Slavery existed because the law built and maintained it, not because the law failed to forbid it.

I remember those days where it would warn if there was any scripting at all, rather than look for dangerous commands first.
Just as a thought, not bothering if the script cannot reach outside of the document itself. Functions that access other files or documents, email functionality, and such triggering the warning instead would have been more effective.

"Apple has never offered a product that justified a large chassis. It used to be lots of slots, hard drives and other storage that justified it. Macs have never been about that"

I see you don't remember the 68k Macs OR the PPC Macs. Apple offered machines with lots of slots ever since the Macintosh II line. HTH.

Too much latency for RAM.

You mean running them on an external GPU? That doesn't take much bandwidth unless you're constantly loading new models.

I tend to agree with the spirit of such comments, but in this case, Apple makes it clear in the TOS that it retains the right to disclose that information if it deems it appropriate. People pay for an anonymity service without reading the fine print :/