Your problem isn't storing the code, it's storing the environment it compiles and runs in. Even if it's plain command line C you're still going to have potenti

Your problem isn't storing the code, it's storing the environment it compiles and runs in. Even if it's plain command line C you're still going to have potential issues with compiler compatibility 30 years from now. C will probably be ok if you code defensively to avoid explicit hardware dependencies, but for all anyone knows C will only be available in museums by then. If it's something high level like Python, it's impossible to guess what state that ecosystem is going to be in 30 years from now. Same applies to operating systems and tooling. Vintage computer museum projects either store the complete hardware and software stack or run old code under emulation. This was easy when you had (for example...) a VAX or PDP-11 that was essentially self-contained. It's going to get harder as processing and dependencies become more and more distributed. I wouldn't even want to assume that something like Docker will look much like it does today, or if it does that it will be compatible with thirty year old images.