Because not all humans strive for honor.

Yep, you’re right — I was just responding to parent’s comment about fiber being best because nothing is faster than light :)

That’s…not really a cogent argument.

Satellites connect to ground using radio/microwave (or even laser), all of which are electromagnetic radiation and travel at the speed of light (in vacuum).

Light in a fiber travels much more slowly than in vacuum — light in fiber travels at around 67% the speed of light in vacuum (depends on the fiber). In contrast, signals through cat7 twisted pair (Ethernet) can be north of 75%, and coaxial cable can be north of 80% (even higher for air dielectric). Note that these are all carrying electromagnetic waves, they’re just a) not in free space and b) generally not optical frequency, so we don’t call them light, but they are still governed by the same equations and limitations.

If you want to get signals from point A to point B fastest (lowest latency), you don’t use fiber, you probably use microwaves: https://arstechnica.com/information-technology/2016/11/private-microwave-networks-financial-hft/

Finally, the reason fiber is so good is complicated, but has to do with the fact that “physics bandwidth” tends to care about fractional bandwidth (“delta frequency divided by frequency”), whereas “information bandwidth” cares about absolute bandwidth (“delta frequency”), all else being equal (looking at you, SNR). Fiber uses optical frequencies, which can be hundreds of THz — so a tiny fractional bandwidth is a huge absolute bandwidth.

80% of the USA lives within urban areas (source). Urban “fiberization” is absolutely within reach.

Agree that running fiber out to very remote areas is tricky, but even then it’s probably not prohibitive for all but the most remote locations.

So the irony is

I see what you did there…

I think you mean more scrupulous, not less.

Hopefully you can publish in an open-access journal — if not it would be great if you could share an arXiv preprint :)

I’d say it gets a little different with command line utilities — maybe “utility” is the appropriate term here, but I’d call something like grep a program, not an application (again — “utility” also works).

To be sure, grep is extremely powerful, but its scope is limited.

Physics is like sex: sure, it may give some practical results, but that’s not why we do it.

— Richard P. Feynman

I think the same is true for a lot of folks and self hosting. Sure, having data in our own hands is great, and yes avoiding vendor lock-in is nice. But at the end of the day, it’s nice to have computers seem “fun” again.

At least, that’s my perspective.

Whatever you decide for your laptop, I’m a proponent of a barebones off-site setup if you’re trying for 3-2-1 backup or similar.

I use a raspberry pi 3 with a single HD (ZFS) retaining some number of daily/weekly/monthly snapshots. Daily rsync, everything over WireGuard+VPS (TailScale would work too).

From our experience in the US, the birth is nothing compared to the financial drain of the other expenses. And at this age, childcare dwarfs all the other child-related expenses.

We have great insurance and don’t rely on family for childcare though, so the math is very very different for someone with “free” familial childcare and no/lousy insurance…

Others mentioned virtualization — I have had issues with COW filesystems (btrfs), as COW does not always play nicely with VM drives (extreme fragmentation and very poor performance).

I don’t know how compensation works in academic administration, but if there’s any vesting going on then you could “take a pay cut” but end up making more due to previous compensation vesting.

Certainly possible for public companies, but again, unsure if that could be the case for a university president…

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.

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…).

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.