News for hackers. Stuff that matters.

A comment on Lisping at JPL (2002). Parent comment

Re:Lisping at JPL (2002) by drongoking on Saturday January 18, 2020 @10:46PM (#22089304)
Sure, just not the abbreviation. "Having a read-eval-print loop running on the spacecraft proved invaluable in finding and fixing the problem."

I shared the reaction, "wow, must've been glacially slow"

[ Parent | on HN ]
Re:Lisping at JPL (2002) by dreamcompiler on Saturday January 18, 2020 @10:52PM (#22089330)
Point taken. I missed that.
[ Parent | on HN ]
Re:Lisping at JPL (2002) by lispm on Sunday January 19, 2020 @06:46AM (#22090882)
Actually the spacecraft being so far away was the reason to put some Lisp system on it. That was one goal of that mission. The software controlled the spacecraft and did not need detailed programs what to do. It would figure out what to do from higher-level task descriptions and what it sensed. Basically a spacecraft as a semi-autonomous robot. Since it was running on top of Lisp, actually LispWorks, it could also be debugged/reprogrammed at a lower level.
[ Parent | on HN ]