3 ms·
Before: In 1994 JPL started working on the Remote Agent (RA), an autonomous spacecraft control system. RA was written entirely in Common Lisp despite unrelenti
by coldtea 3y ago
Before:
In 1994 JPL started working on the Remote Agent (RA), an autonomous spacecraft control system. RA was written entirely in Common Lisp despite unrelenting political pressure to move to C++. At one point an attempt was made to port one part of the system (the planner) to C++. This attempt had to be abandoned after a year. Based on this experience I think it's safe to say that if not for Lisp the Remote Agent would have failed.
We used four different Common Lisps in the course of the Remote Agent project: MCL, Allegro, Harlequin, and CLisp. These ran in various combinations on three different operating systems: MacOS, SunOS, and vxWorks. Harlequin was the Lisp that eventually flew on the spacecraft. Most of the ground development was done in MCL and Allegro. (CLisp was also ported to vxWorks, and probably would have been the flight Lisp but for the fact that it lacked threads.) We moved code effortlessly back and forth among these systems.
The Remote Agent software, running on a custom port of Harlequin Common Lisp, flew aboard Deep Space 1 (DS1), the first mission of NASA's New Millennium program. Remote Agent controlled DS1 for two days in May of 1999. During that time we were able to debug and fix a race condition that had not shown up during ground testing. (Debugging a program running on a $100M piece of hardware that is 100 million miles away is an interesting experience. Having a read-eval-print loop running on the spacecraft proved invaluable in finding and fixing the problem. The story of the Remote Agent bug is an interesting one in and of itself.)
The Remote Agent was subsequently named "NASA Software of the Year".
https://flownet.com/gat/jpl-lisp.html https://flownet.com/gat/jpl-lisp.html
- ykonstant 3y agoThere's some pretty depressing stories in the second half of that article. But more interestingly, the author articulates beautifully one of the main reasons I chose pure mathematics over a programmer career in the late 90s: "One of the reasons I stayed at JPL for twelve years was that I was appalled at what the software industry had become. The management world has tried to develop software engineering processes that allow people to be plugged into them like interchangeable components. The "interface specification" for these "components" usually involves a list of tools in which an engineer has received "training." (I really detest the use of the word "training" in relation to professional activities. Training is what you do to dogs. What you should be doing with people is educating them, not training them. There is a big, big difference.)"
- hdgbkd 3y agoWe just "solve" the problem by training tens of thousands of dogs. Now we have a gigantic dog circus running 24x7. What's mysterious is no matter how many shocks and surprises ever growing complexity produces it doesn't collapse.
- 0xDEF 3y agoWhat is the most Lisp-like type safe language?
- mordae 3y agoTyped Racket probably.
- medo-bear 3y agoCoalton which runs on SBCL
- trealira 3y agoShen has type checking that you can turn on and off. When it's on, it's very much like an ML such as Standard ML. https://shenlanguage.org/ https://shenlanguage.org/ This probably isn't the "most Lisp like," though, even though it does have s-expressions and cons cells. The other person who suggested Coalton is probably right, since AFAIK it's just Common Lisp with static types.
- noaoh 3y agoCarp is a statically-typed Lisp: https://github.com/carp-lang/Carp https://github.com/carp-lang/Carp