Finishing a Dark Souls game.

And finishing a Dark Souls game.

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.

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)

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.

I’ve played all three games. Arch on PC, Lutris, some GE-Proton 9 version. If the camera acts up in ME2, try Gamescope with relative mouse.

EA App didn’t come up. If it causes issues, try an alternatively sourced copy.

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.

Off the top of my head, in no particular order:

• Systemd and its components are responsible for too many essential system functions. Init, services, mounts, timers, logging, network config, hostname, DNS resolution, locale, devices, home directories, boot, NTP sync, and I’m sure there are others, can be handled by systemd or one of its components.
• Systemd violates the UNIX philosophy of “do one thing and do it well”. Systemd is a complex solution to a complex problem: this thread has several comments by a former Arch Linux maintainer that explains why they’ve switched to systemd, and why the earlier method of using single initscripts was unsustainable.
• It is owned and maintained by Red Hat, known for its many controversies.
• Some people just don’t like modern things and think that the Linux ecosystem peaked in the 1980s.

Most (though not all) of the popular complaints are completely unreasonable. Those people usually see themselves as moral and righteous and expect the world at large to follow their personal creed. I especially consider the UNIX philosophy to be outdated, and strict adherence to it to be an obstacle for modern apps and systems.

I have some issues with systemd, and I don’t like that one for-profit company has such a massive influence over the entire Linux ecosystem, but I have to acknowledge that it works, it works well enough to counter my personal issues, and that the people whose opinion matters the most (specifically Debian and Arch maintainers) chose it for a good reason.

Nintendo sees rock bottom as a challenge.