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!

You’re two tubes with a wet sponge between them.

Exactly which flavours of Markdown are targeted/required by this specification?

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

The American mind can’t comprehend the freedom to roam.

This meme became popular in early-to-mid 2020. I’m no historian, but I’m pretty sure there were some things happening in early 2020.

deleted by creator

Forcing mundane objects to think is my second favourite neurodivergent obsessions. Especially when you can make a game run a game that is itself.

My examples won’t work because they’re in code blocks. Code blocks are meant to render their content verbatim, without parsing Markdown tags. This span uses multiple formatting tags. ~~**_This is the same in an inline code span._**~~

~~**_This is the same in a code block._**~~

Like I said, spoiler tags are not a standard feature. Whether they work depends entirely on the renderer used by the client.

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.