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.

The CW folks would presumably be sending QTH instead — I wonder if this graph captures that/if it would make an appreciable difference?

So the irony is

I see what you did there…

I think you mean more scrupulous, not less.

Bonus points: use non-qwerty keyboard for added obfuscation (but keep the qwerty key caps of course).

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.

Note re: mustard. It is not just an “other flavor,” it is also an emulsifier!

It took me a while before I learned this. Even if you’re not going for a mustardy flavor, a little mustard goes a long way in keeping the oil and vinegar from separating. Definitely recommend using some with basically every dressing you make.

That’s what I heard about Chevy’s, 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).

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.

Look, if you don’t want to listen to some random dude who thinks reading is cool, fair enough. But if that random dude also runs level three diagnostics on the warp core and can swap polarity on the main deflector dish with one hand tied behind his back? Yeah…you should probably pay attention.

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’ve been pleasantly surprised by vegan blue cheese dressings, but blue cheese itself…yeah, it’s got a long ways to go.

To each their own though? I can’t imagine why anyone would want something other than i3 (or similar), because almost by definition the DE is not the program I fired up my computer to interact with, and i3 “gets out of the way better” than most others in my experience.

But…that’s just my use case. It’s a horrible UX for most people, just happens to work well for me.

I feel old…when I was learning how to run Linux I started with an old 386 (maybe 486?) my dad wasn’t using. I think it had 32MB RAM, which was fancy for those machines.

We had dial up at the time, so only one machine could be on the Internet. So, I set up a modem on the x86, plugged into an Ethernet hub (switch?), and learned enough ipchains (this was before iptables) to share a connection. It also ran Samba, an AFP server, and probably FTP and HTTP (just for local access) — but it worked for filesharing.

It could also run MP3 streaming software which amused me because the machine itself was too slow to decode MP3 (but that’s not necessary to stream).