Glenn FleishmanThe Voyager probes are amazing in many regards but they may ALSO be the longest continuously running computer programs (by some definitions). Each probe has three computers each of which has a backup. I wrote this eight years ago for MIT Technology Review: https://www.technologyreview.com/2015/08/06/166822/what-is-the-oldest-computer-program-still-in-use/
For more on Voyager probes, see these many articles I wrote about them, including an interview with the original and long-time project lead, Ed Stone. https://glog.glennf.com/blog/2017/8/4/if-you-love-voyager-like-i-love-voyager
If You Love Voyager, Like I Love Voyager
The New York Times has a remarkable article about the Voyager probe team. A number of people who prepared the mission or become involved as it approached the outer planets still log hours every day! I’m an unabashed fan of the Voyager team and the probes they made, which have overper
Michael Busch@glennf @vaurora The Voyager spacecraft are also very obviously the longest distance radio communication systems ever; made possible by rebuilding and expanding the antennas used to communicate with them and by increasing transmitter power as needed - as the team at @canberradsn did this past week.
But now I am wondering where they rank on the list of the longest-running radio links ever. There are older spacecraft that still transmit, but can't receive (e.g. Transit 5B-5 ) and so don't count.
Peter Evans@michael_w_busch @glennf @vaurora @canberradsn
My guess for #3 place in your #Space Radio Lifetime award is ICE, at 36 years. (COSPAR 1978-079A, 12 August 1978 to 16 September 2014.)
They built 'em tough back in the 70's.
My guess for #3 place in your #Space Radio Lifetime award is ICE, at 36 years. (COSPAR 1978-079A, 12 August 1978 to 16 September 2014.)
They built 'em tough back in the 70's.
Elias Mårtenson@glennf the article was very interesting, thanks a lot. It also made me wonder if they have replaced MOCAS yet.
Based on what I know about COBOL software, it's often built as modules in sequences of batch jobs. I work with similar workflows in banking (although not with mainframes) so I've seen attempts to replace large software. Replacing all tge components with a single application in one go is often incredibly difficult. A better approach is usually rewriting individual parts over the course of years.
Computeforloot 
@glennf very interesting