CSS is turing conplete.

You could still NAT between v6’s though.

I care mostly about shell scripting, so I’m focusing on those bits. Via the HackerNews thread, mostly from a-french-anon:

• readlink and realpath
• find -print0, xargs -0 and read -d
• find -iname
• sed -E
• set -o pipefail
• $' ' strings

A few from Itch, Parallel Launcher from Flatpak for SM64 hacks

Also, monetization

If you say “a 10d10”, I know what you mean, but “10d10” is definitely the sum of 10 10-sided dice.

Nope. If you open a nonexistent path and you have permissions to write to that directory, then that file is created.

I grew up with Fahrenheit, but switched my weather app to use Celsius for a while, and I’ve internalized it pretty well. It works fine. The “human experience” angle doesn’t work anyway because that experience is very locale-dependent.

The upside of not changing the I/O is accessory compatibility.

Nope, confirmed different mobo.

16x10 means retro 4x3 games look much better.

I did about once a year until 2018 when I settled on Arch.

But now I’ve got a server on NixOS and loving it, so I might be switching my laptop soon.

I’ve heard that this is what is causing SteamOS 3.5 to take so long.

I run my Nextcloud behind Tailscale, and Caddy handles theTailscale https certs.

xkb has been split off from Xorg, all Wayland compositors (that I know of) use it for mapping.

in the OP

My reply is to a commenter who said they prefer "${HOME}/docs" over both options in the original image ("$HOME/docs" or "$HOME"/docs). Many people prefer to always include braces around the parameter name out of consistency, instead of only when they are required.

My comment explained why my habit is to only include braces when they are necessary.

It’s interesting, the results here are way different than the Code Golf & Coding Challenges Stack Exchange. I would never expect Haskell to be that low. But after looking at code.golf, I realize it’s because I/O on CG&CC is more relaxed. Most Haskell submissions are functions which return the solution.

Sidenote: I like the CG&CC method, it’s semi-competitive, semi-cooperative.

• all languages welcome
• almost all users post “Try it Online”/“Attempt This Online” links
• most users post explanations under their submissions
• often people will post solutions beginning with “port of user1234’s excellent Foolang answer” when there’s a clever shortcut someone finds
• or people will post their own solution with “here’s a solution which doesn’t use user1234’s algorithm”
• or people will add comments to answers with minor improvements

IMO It’s geared towards what is the best part about code golf: teaching people about algorithm design and language design.

This has never stuck with me, and I hadn’t thought about why until now. I have two reasons why I will always write ${x}_$y.z instead of ${x}_${y}.z:

• Syntax highlighting and shellcheck have always caught the cases I need to add braces to prevent $x_ being expanded as ${x_}.
• I write a lot of Zsh. In Zsh, braces are optional in way more cases. "$#array[3]" actually prints the length of the third item in array, rather than (Bash:) the number of positional parameters, then the string 'array[3]'.

This isn’t true. Shellcheck doesn’t insist on braces unless it thinks you need them.

Typically find "$HOME/docs", but with a few caveats:

• In Zsh or Fish, the quotes are unnecessary: find $HOME/docs

• If I’m using anything potentially destructive: mv "${HOME:?}/bin" ...

• Of course, if it’s followed by a valid identifier character, I’ll add braces: "${basename}_$num.txt"