Wherefore?

Some people, for reasons I can only speculate on, don’t like speaking in first person singular. In most cases that I’ve seen, they use “we”. I don’t necessarily agree with the practice from a linguistic perspective, the English language is already a garbage fire as it is without introducing more ambivalent speech… but then I also want to go back to using “thou” for second person singular, so I’m probably not qualified to speak on the matter.

deleted by creator

Even if Galaxy is running under Wine:

• It’s a package manager. It handles downloading files and updates, installation and patching, and verification.
• It integrates various GOG services, like cloud storage for save files.
• It can set environment variables and pass arguments to launched games.

Besides, a Linux-native port doesn’t need to package anything. It can simply mark Wine/Proton and various compatibility solutions as dependencies. Lutris, for example, is still a great utility even if it doesn’t use the packaged Wine versions: all it really needs to do is execute some program in the correct runtime environment with the correct arguments.

If you open the GOG website inside Heroic, it acts as an affiliate link and the HGL team gets a revenue split. An official partnership would still be better, but it’s something.

(edit) Further details here: https://www.gog.com/forum/general/support_heroic_launcher/page1

And Heroic’s GOG affiliate link: https://heroicgameslauncher.com/donate (it uses Adtraction and might trigger some ad blockers)

“Everything is a file” means that many of the system’s components are represented as abstractions in the filesystem. It’s simply an API that allows reading from and writing to it by integrating into the hierarchical file structure.

If you take a look inside /sys, you will find a fuckton of files, but they don’t represent data stored on a mass storage medium. Instead, the directory contains a mounted sysfs filesystem that contains file-like representations of various parts and properties of the system. For example, you can read them like a file by running cat /sys/block/sda/queue/rotational to check if the sda block device is a spinning disk (1) or solid-state storage (0). Or you can write to them like a file by running echo 1 > /sys/block/sda/devices/delete to command sda’s driver to detach the device. Similarly, /proc contains a mounted procfs filesystem that presents information about running processes as file-like entries; /dev contains a mounted devfs that points to various devices; and /tmp and /run contain tmpfs mounts for temporary storage in volatile memory (RAM or swap).

Windows uses various other APIs (like the Component Object Model and others) to accomplish the same that are not necessarily tied into the filesystem.

It follows the same convention as most programming languages that expose the argument list. Python’s sys.argv has the program name at index 0 and the first argument at index 1. C’s char **argv does the same: index 0 is the program name, index 1 is the first argument. So it stands to reason that Zsh’s $0 should be the program name and $1 should be the first argument…

…which, by the way, is exactly what Bash does as well.

That isn’t incorrect, but it’s not as important as people make it out to be. Linux isn’t certified as POSIX-conformant either.

People are way too stuck on POSIX regarding Fish specifically, but in shell scripting, POSIX compliance boils down to “can it run a pure sh script”. Bash is compliant. Zsh is partially compliant and needs to set an option to emulate sh. Fish uses a different syntax and is not compliant; if that is a problem, don’t execute sh scripts in Fish.

POSIX compliance for shell scripts was important in the 80s and 90s when the #! directive wasn’t as commonly implemented and every script might be executed by the user’s $SHELL instead. That is no longer the case as virtually every Unix-like system’s program loader supports #!.

It’s every person’s responsibility to make sure their mom’s (or dad’s (or other parental figure’s)) vibrator runs only secure, trusted software!

My heart bleeds for you, you poor oppressed victim of systemic injustice.

And the worms are winget.

I mean… that’s not incorrect, but…

>>> len("apt update && apt upgrade")
25
>>> len("pacman -Syu")
11

@Mods, please don’t delete this. It’s a valuable lesson.

It’s a combined disability discount: people with hook hands, peg legs, and eyepatches may be entitled to a price as low as 0%.

None of the issues you’ve described are Cargo’s fault. The long compilation time is simply rustc’s compile-time checks (ensuring type and memory safety is much more involved than lexing in GCC), and the number of dependencies to compile is a result of the crate ecosystem. Cargo is just the front-end that automates fetching dependencies and compilation with rustc. Blaming it for slow compilation is like hitting your monitor when the computer is acting up.

It’s called a hyperbole.

(edit) But, honestly, it’s still kind of accurate. Many of the most significant software suites that define the Linux ecosystem in more recent decades were written in the 80s or earlier. X (the display protocol) was released in 1984, and X11 in 1987. GNU Emacs was released in 1985. Vi, in 1976. UNIX System V, from which sysvinit and compatible init systems were adopted, was released in 1983. It’s not a stretch to say that certain people want to regress to the 1980s state, even if the kernel wasn’t around.