Assuming you discover a capsule from the 21st century chances are overwhelmingly that either things have gone great, and you could just ask your AI to create an environment for that old binary (or reverse engineer it), or things have gone badly and you try to bootstrap computing.
The "things have gone average, and I want to run a 200-year old binary" case is I think the least relevant.
But even if we stipulate its relevant enough, this does not solve the issue. The subleq machine does not actually reproduce the hardware environment. A lot of software depends very much on the characteristics of the hardware it runs on. (Timing issue, undocumented but interesting side effects, etc). It depends on bugs in the containing OS. (See Win32 backcompat, e.g.) It depends on quirks and behavior of its input/output devices. Heck, the VM does not even define what "reads a keypress" reads - scancode? ASCII? UTF-8? Value according to numerology?
There's a lot of software that's not amenable to "it's just a single set of numbers in a capsule" with just that underlying VM. Likely most software.
SUBLEQ is a somewhat interesting architecture if you think about "bootstrap compute from scratch", but that's a very different problem.
Several places on that page link to "the napkin", which starts:
> If you are reading this, you have probably discovered a capsule from the early 21st century - a long list of numbers, maybe etched onto a titanium cylinder.
I think this misses a few crucial steps.
Assuming you discover a capsule from the 21st century chances are overwhelmingly that either things have gone great, and you could just ask your AI to create an environment for that old binary (or reverse engineer it), or things have gone badly and you try to bootstrap computing.
The "things have gone average, and I want to run a 200-year old binary" case is I think the least relevant.
But even if we stipulate its relevant enough, this does not solve the issue. The subleq machine does not actually reproduce the hardware environment. A lot of software depends very much on the characteristics of the hardware it runs on. (Timing issue, undocumented but interesting side effects, etc). It depends on bugs in the containing OS. (See Win32 backcompat, e.g.) It depends on quirks and behavior of its input/output devices. Heck, the VM does not even define what "reads a keypress" reads - scancode? ASCII? UTF-8? Value according to numerology?
There's a lot of software that's not amenable to "it's just a single set of numbers in a capsule" with just that underlying VM. Likely most software.
SUBLEQ is a somewhat interesting architecture if you think about "bootstrap compute from scratch", but that's a very different problem.
What? you can write a Subleq interpreter even stoned and drunk. a subleq+ one it's just a simple step over the previous one.
On keypress, yes, they forgot to set that the input and output it's just ASCII, putchar() and getchar() in C.
Several places on that page link to "the napkin", which starts:
> If you are reading this, you have probably discovered a capsule from the early 21st century - a long list of numbers, maybe etched onto a titanium cylinder.
That supposition seems woefully incorrect.
Also will need a pretty big napkin,
https://raw.githubusercontent.com/adriancable/eternal/refs/h...