4 ms·
This article appears on HN on a regular basis, so I thought people might be interested in a bit of historical trivia: the reason this article is called "Lisp as
by lisper 10y ago
This article appears on HN on a regular basis, so I thought people might be interested in a bit of historical trivia: the reason this article is called "Lisp as an Alternative to Java" instead of some other language is that it cribbed the title off my original study (http://www.flownet.com/gat/papers/lisp-java.pdf http://www.flownet.com/gat/papers/lisp-java.pdf). The reason that article was titled the way it was is that I was working at JPL at the time and there was a software crisis underway. To that point, spacecraft had been mostly programmed in assembly language. The then-recently-launched Cassini spacecraft was a notable exception, having been programmed in Ada. But it was becoming clear that neither of these approaches scaled well, and so the hunt was on for an alternative. Java was the hot new language at the time, and it was under serious consideration to become the new standard for spacecraft coding. But Java was new and immature (and, in those days, very very slow), and I was advocating to use Common Lisp instead. That study was conducted -- and the paper was titled -- in order to bolster my case.
Ultimately, Common Lisp flew on a spacecraft once, on the New Millennium DS1 mission. Unfortunately, there was a serious political shitstorm that accompanied that mission, and Lisp never flew again despite several million dollars having been spent to show it to be a viable approach. :-(
- 147 10y agoFor people that are curious about the story behind Common Lisp in space, Stuart Sierra gave a talk at Clojure West that includes that story that I thought was interesting (along with the rest of the talk!) https://youtu.be/-RaFcpNiYCo?t=8m10s https://youtu.be/-RaFcpNiYCo?t=8m10s
- lisper 10y agoA more detailed (and accurate) account: https://www.youtube.com/watch?v=_gZK0tW8EhQ https://www.youtube.com/watch?v=_gZK0tW8EhQ Stuart got one significant factual detail wrong: the race condition was in Lisp code.
- pjmlp 10y agoThat is what I have found in most of my research of computing since Burroughs attempted to use an Algol variant for systems programming. The general opinion is that those systems failed due to technical issues, however most of the time failures are caused by political wars. They are even worse when they are caused by those that don't want things to change, like what seems to have happened during Longhorn development. So one needs a group strong enough monetary and political, to be able to change ways of computing, sometimes even loosing a couple of battles to eventually win the game.
- bluejekyll 10y agoInfo on the Longhorn project: http://longhorn.ms/ http://longhorn.ms/
- pjmlp 10y agoWindows 8 base design is basically Longhorn to certain extent. They brought COM+ Runtime back from the grave, exchanged the COM type libraries for .NET metadata and renamed it WinRT. At the same time C++/CLI syntax was repurposed for C++/CX this time doing AOT compilation to native code. Similarly, .NET went through two new AOT compilation toolchains, first the MDIL binary format used in Windows 8.x, followed by .NET Native introduced in Windows 10. Which begs the question if the Dev and Windows devisions weren't so busy fighting each other, maybe just maybe, Longhorn would have had the UWP application model instead of Windows having gone through all these releases until they had settled their differences. Now it still remains to be seen how much it will eventually matter. This was just an example, there are others regarding other technologies, for example Symbolics had quite a few internal fights. http://danluu.com/symbolics-lisp-machines/ http://danluu.com/symbolics-lisp-machines/
- iamcreasy 10y agoWhat do they use now?
- lisper 10y agoAFAIK (I left JPL over ten years ago), mostly C.
- 616c 10y agoI have seen your essays and finally bothered to look at your home page in your profile. Now you work on SC4? And before JPL and other places of ill repute? When do you kick back and put out low quality, lowbrow work? Haha. I was curious to see Lexicons, and Ciel seems neat, now there is a buildup in systems programming in high level langs. GC-less and system-friendly Lisps are hard to come by, and sadly it seems like work on this stopped a while back. Thanks for all your work, open and closed. I have enjoyed your essays and you seem to be giving us great stuff. Keep it up!
- lisper 10y agoThanks for the kind words. > When do you kick back and put out low quality, lowbrow work? I have gobs of "low quality, lowbrow work" which I don't publish. Too embarrassing. But I kick back a lot. Lisp is a huge lever that allows me to appear a lot more productive than I really am :-)
- 616c 10y agoSome of us can be unproductive, Lisp or not. Despite all the jokes I can profer on HN in this trendy topic, some of us are destined to suck at programming, from Assemly to PHP to Datalog to J!
- lisper 10y ago> some of us are destined to suck at programming That sounds like a self-fulfilling prophecy.
- gte525u 10y agoOut of curiosity - what caused limitations of scaling ada?
- lisper 10y agoI'm not sure. I've sent out some inquiries to the people I know who actually worked on Ada code back in the day. If I get a response I'll post it here.
- gte525u 10y agoI appreciate that
- lisper 10y agoOK, I got a reply, but it was off the record so I can only pass along my own interpretation of it here. It turns out I was wrong when I said that the reason Ada didn't get used more was that it didn't scale. It did. It worked just fine on Cassini, and there was no reason based on that experience to believe that it wouldn't work on other spacecraft. The reason it wasn't used more turns out to be the same reason Lisp wasn't used more: politics. Cassini was being developed at the same time as the Pathfinder mission Because Pathfinder was done on a (relatively) low budget, they used C because it was easier and cheaper to get C coders and compilers than Ada coders and compilers. Pathfinder was seen as the way of the future while Cassini was perceived as part of the stodgy (and expensive) past, so subsequent missions were built on top of the Pathfinder C code base and not the Cassini code base. Ironically, it was the same event that killed Lisp which also killed Ada, though the effect was less direct. The Remote Agent was originally going to be the mainline software that controlled the entire DS1 mission. But when it became clear that the RA would not be ready in time, management decided to demote the RA to a flight experiment and adapt the Pathfinder software to run the DS1 mission. Because the Pathfinder mission itself was over, the team was available, while the Cassini team (the Ada folks) were still busy working on Cassini. By the time the Cassini mission ended [1] and the people with Ada experience became available again, C was already entrenched as the new de facto standard for slight software. The success of the subsequent Mars missions, and particularly the spectacular success of the Mars Science Laboratory EDL (which, I have to say, was freakin' amazing) further cemented the status of the Pathfinder approach to software development. I have to give the C folks a lot of credit here: they have produced an awful lot of very reliable code for a very long time now. But I still think they're playing with fire. [1] The Cassini software development team actually became available before the end of the mission, but they were still needed through the Saturn oribit insertion in 2004.