You’ll have to put that spoiler in a new paragraph. Unfortunately spoiler tags are not a standard Markdown feature. There are no inline spoilers in the Lemmy UI (which is a stupid ass decision, what the fuck devs), and no spoilers whatsoever on Mastodon.

This works:

:::spoiler Spoiler Title
spoiler content
:::

This does not:

:::spoiler spoiler content :::

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

The more I learn about biochemistry, the less it seems like black magic fuckery and more like a middle aged bloke with an angle grinder and a welder going at molecules until they look kinda right. NileRed’s rubber glove hot sauce is partly to blame.

Add it to the list of reasons to hate Henry Ford. When he needed a new screw standard to replace slotted screws in his factories, he went to Robertson first, but he wasn’t willing to sell production rights to Ford. His second choice, Phillips, took the offer. Phillips and similar cruciform screw heads (Pozidriv and JIS, both of which are superior to Phillips) proliferated globally because of this, and it would take a massive shift in the industry today to fully transition to Robertson or Torx.

It wasn’t designed to strip when overtorqued. It’s a myth with no evidence. The original patent says nothing about it (I’ve read the whole patent), and later patents list it as post-hoc justification for a design fault.

let you build faster like Python

I have to write so much boilerplate code to make sure my objects are of the correct type and have the required attributes! Every time I write an extension for Blender that uses context access, I have to make sure that the context is correct, that the context has the proper accessor attributes (which may not be present in some contexts), that the active datablock is not None, that the active datablock’s data type (with respect to Blender, not Python) is correct, that the active datablock’s data is not None… either all that or let the exception fall through the stack and catch it at the last moment with a bare except and a generic error message.

I used to think that static typing was an obstacle. Now I’m burning in the isinstance/hasattr/getattr/setattr hell.

My only issue with hex is that the angles between the sides are too flat and easy to round off, especially if the screw is small or cheaply made (soft steel or aluminium). Speaking from experience, if the screw head is 3mm across or smaller, Torx or JIS (which is still better than Phillips) are more reliable.

Philips is designed to allow the screwdriver to slip out

That’s a myth. I’ve read the entire patent and there is no mention of it, and later patents are just post-hoc justifications for an objectively faulty, inferior design.

My charitable hypothesis is that the design uses shallower angles that are easier to cam out because sharp angles would result in stress fractures during the cold forming of the screw heads. My realistic hypothesis is that dies with shallow angles are cheaper to produce and more durable. But the point is moot: the Phillips didn’t become the de facto standard because of any practical advantage (real or perceived), but because Robertson wasn’t willing to sell exclusive rights to Ford.

I’m usually not one to criticise a person’s life choices, but if you think Phillips is better than the popular alternatives, I immediately think less of you as a person.

@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%.

I am thankful for Forkknife because most of the annoying kids who made Minecraft cringe are now playing that instead.

Here’s a link that doesn’t ransom your private data: https://archive.md/lO08a

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.

Are you sure? The last time I saw him, he was positively gushing.

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.

Not a single patch of snow to shovel. Truly we have peaked as a species.