It looks like it might be even older than that, it looks like Enrico Fermi may have started it in 1947 (a note in the introduction of http://arxiv.org/pdf/1207.5076.pdf).
--- At Los Alamos, Monte Carlo computer codes developed along with computers. The first Monte Carlo code was the simple 19-step computing sheet in John von Neumann's letter to Richtmyer. But as computers became more sophisticated, so did the codes. At first the codes were written in machine language and each code would solve a specific problem. In the early 1960s, better computers and the standardization of programming languages such as Fortran made possible more general codes.
[..]
MCNP5, released in 2003, is rewritten in ANSI standard Fortran 90. It includes the addition of photonuclear collision physics, superimposed mesh tallies, time splitting, and plotter upgrades. MCNP5 also includes parallel computing enhancements with the addition of support for OpenMP and MPI. Large production codes such as MCNP have revolutionized science − not only in the way it is done, but also by becoming the repositories for physics knowledge. MCNP represents over 500 person-years of sustained effort. The knowledge and expertise contained in MCNP is formidable. ---
So it seems that Fortran is already the 50-year programming language.
[1]: https://laws.lanl.gov/vhosts/mcnp.lanl.gov/pdf_files/la-ur-0...
1. The program itself.
2. The behavioral specs for the program.
3. The behavioral specs for the runtime environment.
4. The configuration specs for the runtime environment.
Somewhat hidden in there is the ability to read an aribitrary program, transmute it to another program. That can be hard--especially with a language like C++, where significant computation can occur during compilation.There'd probably be cases where it'd fall short of that capability, but ultimately, if the desire is to make sure you can run an arbitrary current program on an arbitrary future computer, you probably have to get pretty close to that.
With lisp macros setting up everything?
Out Of This World has survived, a couple decades of frenzied developments, as has Doom and Quake and Adventure and Zork. That gets you around the 20-30 year mark.
I'd look at old Unix utilities like awk and sed. That gets you around 40 years.
I'd look towards the banking industry at old COBOL credit-card processing and reporting code. That gets you into around 50 years.
The interesting thing to note is that in the first two cases, long-term support was caused by reverse-engineering and by having the source available to port. As long as there is a machine with an integer unit, we have Doom. As long as there is a floating-point unit, we have Quake.
The third case, though, relies on turducken VMs of 360s running on 370s running ZMachines running on...whatever comes next. For long-term support, one wonders how tenable this is.