Single quotes don't allow any escaping in shell, you need

'I don'\''t know what you mean, I'\''ve never encountered any annoyances'

Or, in Zsh with setopt rcquotes:

'I don''t know what you mean, I''ve never encountered any annoyances'

I get annoyed by differences with (Ba|Z)sh when I try Fish, but nushell is so much its own thing that it's fun.

Scrubbing through the video, this hurts my soul

echo $(echo $STRING | sed 's/World/Bash/')

For variables bash has PE forms:

echo ${STRING/World/Bash}

I miss these too much when I try Fish.

The "$@" doesn't do that you think it does in an alias. It gets expanded on alias creation.

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

8GB memory + two Firefox profiles makes things difficult on my laptop.

I get your point. Since a .tar.zst file can be handled natively by tar, using .tzst instead does make sense.

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.

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"

My Linux review: 10/10, would recommend, but would not install for someone and let them use it for the next 5 years.

With embedded terminal escapes? True evil indeed.