6 ms·
Even aside from the apocalypse, I was wondering recently how someone might "pass down" some piece of software, like say a video game, to their descendants. If y
by kibwen 4y ago
Even aside from the apocalypse, I was wondering recently how someone might "pass down" some piece of software, like say a video game, to their descendants. If you want to leave a written record for future generations then it's easy enough to print out a book on some acid-free paper and reasonably expect that it will last for up to a millennium. But for robustly archiving a piece of software it's not enough to print out the complete source code (including dependencies), you also need the complete source of the compiler (including dependencies), and the complete source of the operating system it runs on, and complete schematics for the hardware it runs on, and instructions on how to manufacture the hardware, and possibly more.
In the same way that we have standards for archival-grade books, it seems like we could benefit from some sort of standard archival-grade software stack designed for simplicity (and I mean real simplicity, I agree with the article that even C is too complicated and you want a Forth or something (or maybe a Scheme)). It's okay if the stack is as slow as molasses, as long as you have a functional reference implementation you can always produce a translation into whatever modern stack exists in your time period.
- jayhoon 4y agoWould a technical description in plain English (specification) and C code be sufficient to preserve a piece of software? The understanding of the specification may be different years later, but this applies even to the paintings and the works of fiction. So, the question is not only about the preservation the actual software, but also about its correct interpretation.
- vharuck 4y agoSort of like how the valuable parts of math textbooks are the theorems and proofs, with the problem sets (i.e. implementations) being nice but arbitrary extras?
- jayhoon 4y agoThis is an interesting angle on essentially the same problem. Can a set of theorems about the prime numbers lead another group of people to the RSA encryption, for example? Considering that Clifford Cocks invented a similar system 4 years before Rivest, Shamir and Adleman (and even before Diffie and Hellman published their cryptosystem), the answer seems to be "yes". On the other hand, that 4 year difference means that people have to be ready for the idea, i.e., work on their "problem sets".
- cableshaft 4y agoI think for simpler games this idea works well, yeah (and I tend to design simpler games, so I might have to start doing something like this). One of my old games, Proximity, ended up in a couple chapters on a book on an old book about Flash development, I think it was called Actionscript 3 Design Patterns. You could make the original game pretty close from there (even though it was someone else that reverse engineered it and did it somewhat differently, it still got the job done). But that game is pretty darn simple, just a hex grid where you draw a tile from 1-20, and wherever you place it, it'll capture tiles of an opposing team surrounding it if the tile you placed has a higher number than them. I've worked on tweaking the formula in a bunch of a ways over the years, but that's the core mechanism. Once a game gets complicated enough it gets a lot harder to ensure that all of the nuances in the code, edge cases, hacky shit to get the game out the door, etc, so it's going to be more limited. But I'd still love to see a series that did this for more games though (I know one guy did it with the Quake source code and a couple other Id games).
- GrinningFool 4y ago> The understanding of the specification may be different years later, but this applies even to the paintings and the works of fiction. That's an interesting parallel. But for it to be equivalent, I think it would have to be to the method of creating those paintings/works of fiction. Instead of passing down the Mona Lisa, you're passing painstakingly detailed instructions detailing how to make the Mona Lisa.
- AeroNotix 4y agoIt's called a disk snapshot.
- mtlmtlmtlmtl 4y agoI don't know about you, but I don't normally have the source code lying around on disk for: the compiler and its dependencies Any dynamically linked dependencies and whatever extra compilers they might need Other potentially necessary things like build tools and source control systems
- microtonal 4y agoI am not sure if this is still the case, but the FreeBSD (and OpenBSD) CD sets and DVD used to contain the full source code of the base system and it’s easy to rebuild the system from source. BSD also works on relatively modest hardware.
- elcritch 4y agoThere are also https://bellard.org/tcc/ https://bellard.org/tcc/ and https://github.com/jserv/amacc https://github.com/jserv/amacc that contain mostly complete C compilers.
- int_19h 4y agoIt's not hard to arrange these days, if one really cares. I have a local mirror of Debian main + contrib + non-free packages, source + i386 + amd64 for every package. It's 200 Gb - a $20 SD card can handle that. How many copies would you need to make for at least one to last N years?
- qwerty456127 4y agoI am most worried about the hardware. I am afraid we will have to start all the progress completely from scratch.
- speed_spread 4y agoIMHO, modern microcontrollers is where it's at when it comes to preserving the current technological base. They're 32 bits and relatively high powered, yet cheap and reliable enough. They don't need cooling and are robust to be fed from different power sources. If you base your software stack on, say, the ARM Cortex M4 or even M0+, you should be good for long time. You can stash a lot of spare parts and can maintain boards using simple soldering techniques.
- kevin_thibedeau 4y agoDevices running on high density flash will not be reliable long term. None of these devices have ECC to reduce the probability of catastrophic failure from accumulated bit flips.
- speed_spread 4y agoI was thinking more about devices that can be repaired by changing a failed CPU than devices that have a lower failure rate. I believe STM (and others surely) has a line of "process critical" MCUs that may have additional reliability features but these chips are built in much lower quantity and are much pricier. It's a tradeoff that would need to be evaluated for sure. Preferring external flash to on-chip storage would also help. Some ECC can also be performed in software where warranted.
- makapuf 4y agoProblem is that stm32 parts are currently in a kind of post apocalyptic state, speaking of supply chain
- elcritch 4y ago
- FartyMcFarter 4y agoThe most reliable way to do this is with emulators. A full emulator is a complete description of some hardware and software combination. If we can keep emulators working on modern hardware and OSs, we can guarantee that most old games will be playable indefinitely. For example, if you have dosbox you can play a lot of old MS-DOS games without having an x86 CPU or DOS itself.
- Kadin 4y agoPrinting the source out on paper would probably be the most long-lasting storage method (aside from engraving it into large pieces of stone, maybe). But typing the source code back in for most non-trivial pieces of software would be really painful. "Here's the source code, go type it in" hasn't been a very popular method of distributing software, for good reason, in a long time. Maybe there's some way that you could include the true source code (in C or some other well-understood language) of a small decoder program, which would then take as input some more-compact representation of the desired programs? Something minified and compressed, but kept in a form that would make it relatively quick to type in? Maybe you could have the user type in groups of characters (6-7 or so at a time, because that's generally assumed to be the number of abstract symbols a person can easily hold in working short-term memory) and get a checksum back, that they could verify against the input book. Actually, you should probably have checksums per-line, per-page, and per-chapter/section. That way if you had a decoding problem, you could quickly drill down to the error without manually checking each character.
- cardanome 4y agoOr you could just use APL, which already has a high information density. Lot's of useful APL programs are very small, easily fitting on a single stone table and would not be much trouble to retype. In fact good APL programmers are even able to memorize them easily.
- jeremysalwen 4y agoYou might be interested in this superuser question: https://superuser.com/questions/415451/how-to-transfer-a-file-over-pen-and-paper-with-error-correction https://superuser.com/questions/415451/how-to-transfer-a-fil... I was thinking forward error correction would make interactivity unnecessary.
- Banana699 4y agoSaving the source alone hardly solves anything, the comment you're replying to highlights the real problem : The Stack. Everything from the compiler\VM to the OS to the instruction set architecture and everything in between. You have to save and store all of that. You need a format other than text, text is extraordinarily inefficient and lossy at anything that is not declarative factual information. There has to be artifacts.
- ifyoubuildit 4y agoI think you could design a device that optimizes for longevity. Build the cheapest, simplest device that can run your piece of software, and then produce lots of them. On the simplicity side, all of the parts would be solid state, it would handle whatever power you have on hand, the inputs and outputs would allow for using whatever devices you could cobble together in a post apocalyptic world. Then on the software side, every one of these devices could easily export a standard image that could be used to build another device. A lot of handwaving here, but most of what we sell these days is basically disposable because that's what is incentivized. If we actually optimized for longevity, we could probably do some amazing things. Edit: for bonus points, each device will include detailed technical documentation on how to produce the device itself from scratch. It could be a sort of rosetta computer.
- NegativeLatency 4y agoSo a 6502(C)?
- AstralStorm 4y agoDon't forget the BASIC interpreter. The problem is that making any computer smaller than a big cabinet requires large scale integration microchips, notoriously hard to make, and potentially replace. So it's going to be closer to PDP-7. You can do quite a lot with this sort of machine in an industrial setting.
- ifyoubuildit 4y agoWhat's the life expectancy of an integrated circuit? I was thinking make tons of them and the odds are that some percentage of them would still be functional long into the future, assuming you package them up nicely.
- int_19h 4y agoOP is suggesting premaking such devices in large enough quantities that you'd just rely on them for the foreseeable future to run that legacy code.
- bitwize 4y agoFun fact: PCs used to come with nearly all this information. Full schematics, manufacturer specs for the CPU and other important chips, all in the Technical Reference Manual. The same with Tandy computers: provided you could source the components, you could build your own Tandy 1000 or 2000 with the information in the manual. It's an absolute crying shame that computers do not come with this level of documentation anymore. It's not even available. There are probably parts of your computer that the "intelligence community" goes to great expense to ensure you know nothing about.