Ouch! Guess you got me on that one Kelly. But I thought your issue was the reinvention of new langauges. I thought your claim was sort of that language doesn't matter, let us just stick to one so we don't have to relearn a new one all the time.

I remember you made a remark about the Apollo program using Fortran and us not being able to read that. If you where okay with sticking with 1950s Fortran I am not sure why you would label Go as trash.

And anyway I am not sure how much Fortran code was used. Probably in the planning of trajectories and such. However e.g. the Apollo 11 guidance computer was written in assembly code: https://github.com/chrislgarry/Apollo-11/blob/master/Luminary099/AOTMARK.agc

The reason that code is hard to read is because it is very low level. But at least they did something which seems to have gone out of style in these days, which was judicially commenting their code. That actually does help a lot in preserving code for the future.

I knew a guy that worked on code controlling a subway. It was from the 1950s but it was still highly maintainable because each code file came with a documentation file, describing in detail what the correspondingly named code file did.

If people want to preserve their code for future readers they should care less about language and more about documenting and commenting their code properly.