from stdlib.h import cout

Wait this looks wrong, shit…

Anything can use it, but I think by convention it’s used for http on a non-privileged port.

Maybe there’s some interplay between amd64 and x64 architectures.

AMD64 and x64 are the same thing. Do you mean AMD64 and x86? There is definitely interplay there, as AMD64 implements the x86-32 instruction set.

Same — rsync to a pi 3 with a (single) ZFS drive at family’s house. Retain some daily/weekly/monthly snapshots.

I have a (free) VPS with static IPv4 which is how I connect everything.

Both the VPS and the remote site have limited network speed (I think 50Mbps for VPS), so the initial sync was done sneakernet (well…“airplane net”). Nightly rsync is no problem bandwidth-wise, and is mostly just any new videos I’ve uploaded to my local Immich instance.

Sounds like the opposite reasoning may have some truth:

“Cardinal George of Chicago, of happy memory, was one of my great mentors, and he said: ‘Look, until America goes into political decline, there won’t be an American pope.’ And his point was, if America is kind of running the world politically, culturally, economically, they don’t want America running the world religiously. So, I think there’s some truth to that, that we’re such a superpower and so dominant, they don’t wanna give us, also, control over the church.”

Nah just give them the .tex source and let them deal with it.

It is “backwards” from some other commands — usually you run copy/rsync/link from source to destination, but with tar the destination (tarball) is specified before the source (directory/files).

That, and the flags not needing dashes always just throws me for a loop.

And the icing on the cake is that I don’t use tar for tarring that often, so I lose all muscle memory (untaring a tgz or tar.bz2 is frequent enough that I can usually get that right at least…).

I just wish we’d have neither inflation nor deflation.

Some tech has followed this pattern. For example: entry level Mac laptop in ~2000 was the iBook, priced at $1599 ($3k+ in today’s dollars). The current entry level Mac laptop (M4 Air) starts at $999 — cheaper in absolute dollars, and way cheaper in relative dollars.

(Macs are just an example since Apple doesn’t have a very extensive product list, so there’s only one “entry level” laptop to choose from. And yes it’s fair to ask if the relative specs have just gotten worse, but I think this is also the opposite — the iBook was iirc criticized as being underpowered, whereas the M4 Air is afaik well regarded.)

I am the Walrus?

Interesting, TIL — thanks!

Books has become e-books.

To some extent — but have you been to a hip bookstore recently? They exist, and are very much alive.

Cashless requires power all the way from PoS to wherever the servers live.

Edit: see below

It makes for a mean cappuccino, and is environmentally much, much lower impact.

You mentioned ham radio — definitely fun! It’s a process to get into it though, as you need to study/pass an exam, and then you need a radio. Radios range from cheap ($25 or so) in the VHF/UHF (“walkie talkie”-style) to more expensive for an HF rig ($1000 range for 100W HF). If you want to get into low power (“QRP”) it can be much cheaper. You also need a fair amount of space for a good antenna setup…

There are tons of different communication modes, some without a computer and, like you mentioned, some that use computers. wsjtx and fldigi are popular programs.

Good luck!

I could be wrong but I think these are prepaid, not paid on delivery…

“…and there are no comments, because it’s Self Documenting™”

Modern bots are bad, but the old school IRC (maybe early Battle.net?) bots… I’m cool making an exception for them if you are.

CC “debt” that’s paid off in full every month is debt in the same sense that eating at a typical restaurant puts you in debt.

Don’t get me wrong, unmanageable CC debt is a real thing, but that’s not what we’re talking about.

A lot of non-graphical utilities — basically the *NIX coreutils, plus stuff like rsync, ssh, compression/archival tools (tar, gzip, bzip2, etc.), grep, and the like. Git also comes to mind.

I think part of this is that the UNIX philosophy is “developer friendly” — tell a good dev they need to make a compression utility that follows this protocol, and they will make a compression utility that follows the protocol.

Having a CC doesn’t mean you have debt…