It’s interesting that, with Python, the reference implementation is the implementation — yeah there’s Jython but really, Python means both the language and a particular interpreter.

Many compiled languages aren’t this way at all — C compilers come from Intel, Microsoft, GNU, LLVM, among others. And even some scripting languages have this diversity — there are multiple JavaScript implementations, for example, and JS is…weird, yes, but afaik can be faster than Python in many cases.

I don’t know what my point is exactly, but Python a) is sloooow, and b) doesn’t really have competition of interpreters. Which is interesting, at least, to me.

Did the developer use any version control though? SCCS has been around since the early 70s, RCS and CVS since the 80s. The tools definitely existed.

Also, it was a single dev, which makes SCM significantly simpler!

My recollection is that the DVD included that library, but it’s been a while…

…are Turing Complete, so what you can do with them is exactly equal.

But they’re only equal in the Turing complete sense, which (iirc) says nothing about performance or timing.

Awesome, thanks for the detailed answer!

Don’t forget Pinarello! Gorgeous and, last I checked, very well regarded. Just make sure your wallet is prepared — you can definitely drop $15k on a well-spec’d Pinarello Dogma.

I just wish they made toddler clothes in my size.

Do you still start in 1st? Do you skip gears?

I hope I’m wrong! I’d definitely consider buying some — hopefully you can report back with results. If they’re slower than advertised but have the actual capacity that’d still be awesome!

This looks like it might be it:

https://www.tomshardware.com/pc-components/ssds/buyer-beware-fake-samsung-1080-pro-4tb-ssd-promising-unbelievable-158-gbs-speeds-for-dollar43-is-too-good-to-be-true

The drive doesn’t provide 4TB of storage either, considering the single NAND chip. That means if you were to attempt to write that much data to the SSD, at some point it would either fail or start overwriting existing data.

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.

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.

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

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!

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

I’m curious what you’re doing on an SBC that explicitly requires x86, though?

Not parent, but I used ARM SBCs for a bit, and while it was nice, my x86 experience with a nuc has been much, much better. HW acceleration works on some RPIs, and sort of worked on my Orange Pi 5+, but only when using an ancient kernel which had some hacks (like, kernel debug messages saying “DISABLE THIS FOR RELEASE!”). And afaik RPI 5 doesn’t support hw encoding (not to mention no SSD support).

Basically, my experience was that the hardware was neat if sometimes limited, the energy consumption was great, but the software/kernel support…ugh. YMMV of course.