That's funny, I first thought about paper. http://www.bitsavers.org/ http://www.bitsavers.org/ is a famous archive of vintage computing software (and hardware d

That's funny, I first thought about paper. http://www.bitsavers.org/ http://www.bitsavers.org/ is a famous archive of vintage computing software (and hardware documentation), and it is just a large folder of PDFs. In contrast, when I browse https://archive.softwareheritage.org/ https://archive.softwareheritage.org/ it feels like a combination of Github and the Wayback machine (https://archive.org/ https://archive.org/). How do they intend to archive the generated documentation of software? How do they intend to keep this stuff running? How do I even "run" a generic code for something in an arbitrary github archive? Just storing and presenting git repositories nicely doesn't sound like a breakthrought, especially if it is a clone of github, i.e.