12 ms·
The rise and fall of Lisp at the Jet Propulsion Lab (2002)
- deleted 4y ago[deleted]
- myth2018 4y agoI've read this article some years ago and always wanted to ask: besides size, what were the arguments against Lisp in JPL? Author's position is biased, as he recognizes, then I'm curious about the other side in this story.
- dagss 4y agoI used to be a fan of programmer productivity and having the best tools to express ideas in. In our case, this is not about LISP, but about being able to write 40 lines of SQL in half an hour to solve things that other people reach for 1000 lines of backend language to do. But also trying hard to identify opportunities to simplify and delete code instead of adding another layer of complexity on top every time something doesn't add up. But I've started to wonder. In some ways I feel "our" area in the company has been a victim of our own success: By doing things in smart/efficient ways, the tasks we've done has become seen as simple, we didn't need to recruit as much, and eventually because of the low number of people occupied on the task in the organization it is seen as easier or less important and we are more vulnerable to churn than larger teams. I've seen simpler problems getting solved in (what I think is) very inefficient ways and I used to scoff at that. But now I think what they gain is a large robust team, which can handle both churn and have more weight politically in the organization. Solving something inefficiently simply offers a way to have more people do the same task, for redundancy. In a sense, once an organization hits a certain size it seems that efficiency in a programming language is an anti-feature. You WANT a larger set of programmers to be happily working on something just to have a larger team around the code and redundancy in people. If a programming language / environment allows you to be too efficient, then too few people get the job done and you become vulnerable. At least, that's the best explanation I have at what's really going on in the industry.
- taeric 4y agoThis sounds like the standard "but are they busy?" concern hitting. Folks claim they want folks that are working "smarter" and not "harder." Completely ignoring that that is, itself, hard. I agree with your general concern. I hate it when, not only do I know that I am in fact lazy, but that is not why I have done less in this case. I genuinely believe the smaller solution is far far preferable. All too often "don't do it" is by far the better option for what so much internal tooling does. To that end, I push back against you wanting a less efficient language. I think efficiency is itself a trap. Redundancy and general pacing is a good thing. Languages that try and forego that are not doing themselves any favors. But, and this is fully to your point, if you don't have the spots in your organization that are fully tolerant to mistakes and bad ideas, than you don't have room in your organization to grow. And if you don't have room to grow as an organization, than you probably don't have room to grow the software, either.
- pmarreck 4y agoI'm still a fan of the things you mentioned in your first paragraph, and your analysis here horrifies me. I really, really, really don't want this to be true, or to be perversely incentivized.
- macintux 4y agoYou see related issues with operations too. I was contracted to a company using WebSphere, and they had 4 people (including myself) doing very little except tediously deploying applications to the clusters. So I took a chunk of my downtime and wrote a deployment engine, to eliminate some of the common mistakes, and ideally make things much faster/predictable. In hindsight I can see why the team didn't like the idea: in addition to the new Perl code that someone would have to support, it was a serious risk to their jobs. If deployments that previously took 2-3 hours of tedium were reduced to 20 minutes of scripting, why would they need 4 people to do it?
- bmitc 4y agoWas Lisp actually ever risen at JPL, or was it just used on these handful of projects by a single or small group of developers? > 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. I like Lisp and am certainly no fan of the complexity of C++, and barely know it because of such, but is this the conclusion that should be taken? Porting an existing and in-work application from one language to another, with the two languages being rather wildly different, seems like trouble from the start. It doesn't address, however, the idea of starting from the beginning with another language. The conclusion quoted seems to skip over the possibility of using another language from the start.
- spicybright 4y agoI'm going to straw man a bit, but it feels like lisp enthusiasts are desperate to find stories of commercial software being written in lisp. I'm sure there's many examples I haven't heard of that are legitimate (using lisp for almost all of a specific domain at scale and having a mature codebase, tho that's arguable) but I've yet to see any example that has meat on it's bones, besides the company that did crash bandicoot on the PS1. And even that one I'm unsure of as I feel it's been mythologized with how often it's pointed to. I don't blame them though, I root for lisp very much. I'd rather see this articles like this posted and picked apart for validity vs not hearing about them at all.
- kaveh808 4y agoThe one genuinely successful Lisp company I can think of was ITA/Orbitz. They were acquired by Google, who AFAIK still maintains the Common Lisp code base.
- jjtheblunt 4y agoAutodesk cad cam ? Was that not Lisp?
- xarope 4y ago
- pmarreck 4y agoIs every "advanced" language doomed to fail? (where "advanced" means: a paradigm that results in greater economy of code per unit of work done, easier debugging, easier testing, complete elimination of entire classes of bug (such as in an immutable language), easier maintenance etc...)
- 082349872349872 4y agoStructured languages didn't fail, and OO languages took over a few niches.
- pmarreck 4y agoYes, but OO languages create the same spaghetti-code morass that imperative languages did. As opposed to, say, functional languages, for which it seems far harder for some reason to create spaghetticode
- deterministic 4y agoSome of the cleanest code I have ever seen was written in C/C++. And some of the worst spaghetti-code I have ever seen was written in C/C++. Bad developers write spaghetti-code. Languages don’t write anything.
- pmarreck 4y agoOut of curiosity, can you point me to some of this very clean C/C++ code?
- deterministic 4y agoIt’s all proprietary unfortunately. However the Doom C code available online is nice and clean.
- revskill 4y agoI think it's about explicitness vs implicitness.
- lisper 4y agoAuthor here. AMA.
- deleted 4y ago[deleted]
- SOLAR_FIELDS 4y agoHow do you feel about Lisp in 2023 compared to your opinions as expressed in the article? How do you feel about Clojure? I’m a seasoned software engineer in 2023 that has worked up and down the stack that has always wanted to get into Lisp. What’s the 2023 way to do it?
- lisper 4y ago> How do you feel about Lisp in 2023 compared to your opinions as expressed in the article? I feel pretty much the same way today as I did then. > How do you feel about Clojure? I've never used but, but from what I've read it looks pretty spiffy. > I’m a seasoned software engineer in 2023 that has worked up and down the stack that has always wanted to get into Lisp. What’s the 2023 way to do it? Just do it. There are a zillion Lisps to choose from and a zillion tutorials and books, just pick one and start writing (or, even better, reading) some code. My personal favorite is Clozure Common Lisp on a Mac. For a starter text, PG's and PN's (Peter Norvig) books are pretty good. But nothing beats just picking a little project and building something.
- adastra22 4y agoHave you done more with Lisp since then? (Your username suggests so)
- lisper 4y agoYes, a lot. In fact, for the last 5-6 years I have been working to help develop and maintain a tool for VLSI chip design written in Common Lisp. (Unfortunately, the company that built it was recently acquired by a large publicly traded corporation, and they have decided to kill the project. Plus ca change, plus c'est la meme chose.) I have also done a lot of personal coding in CL. Most recently I wrote a spam filter that I use in production on my personal mail server.
- FpUser 4y agoEvery time I hear about JPL Qian Xuesen comes to mind: https://en.wikipedia.org/wiki/Qian_Xuesen https://en.wikipedia.org/wiki/Qian_Xuesen.
- josephshaw92 4y ago[flagged]
- noobermin 4y agoNowhere near the same situation but the same spirit, a lot of computational science still uses fortran (f90, thankfully for more modern codes) and has resisted the push to use C++ like everyone else. Fortran still is the right tool for numerical software, so it's good we avoided the bandwagon.
- kqr 4y agoA relative of mine had a huge fight at work a few years ago with younger management who wanted to re-write the core of their simulation software in Java, instead of maintaining the Fortran code. I trust his judgment when he said it would be a bad idea.
- ngcc_hk 4y agoWhat computer language is used in those star*. projects. That might afford the implicit claims the last paragraph.
- deterministic 4y agoI am always surprised when I read this kind of article. In my mind a good software developer will figure out how to be productive and get things done in any programming language. I have often worked with programming languages, editors, operating systems etc. that weren’t my #1 choice. However I have usually been happy and productive, using code generation, editor tools or whatever to automate the things I don’t like. You love Lisp and hate Java? Great! Use it to generate the Java code you don’t want to write. And be smart. Don’t tell management you are using Lisp. If they ask why you are 10x more productive than anybody else, just say you are using a code automation tool to be more productive. Which is true! Or simply shrug your shoulders, and humbly say ”years of experience” :) The developers I admire and want to hire are the ones that can be thrown into a shitty disaster area where everything is broken, and all the tools are unfamiliar and crappy, and still somehow manage to turn it around and fix it. They are f*** heroes. The software developer equivalent of the Navy Seals.
- kazinator 4y ago> to be productive and get things done in any Yeah, but the question is how productive are those things that are getting done. A 100% productive assembly language programmer is not the same as a 100% productive Python programmer.
- deterministic 4y agoThat might be true for some developers in some contexts, but it has nothing to do with the point I am making.
- kazinator 4y agoIf you don't like Java and generate your way around it, that's not a genuine measure of productivity in Java. Just like using a HLL (which generates machine language) isn't a measure of machine language productivity. Whatever approach you settle on is a language. E.g "Bob's Lisp-based Java Generator" is a language. It's neither Java, nor Lisp. That language helps give Bob a certain productivity. What Bob is doing represents the vast minority, and could create a maintenance problem for the organization, and its army of people who know only Java. Code generation isn't a practical recipe by which every programmer everywhere can hit productivity in any language.
- AceJohnny2 4y agoI believe the original author posts around here, @lispm IIRC?
- dang 4y agoUpdated last year (edit: no it wasn't), so I've left the date off this one (edit: no I haven't). Previously: Lisping at JPL (2020) - https://news.ycombinator.com/item?id=28113434 https://news.ycombinator.com/item?id=28113434 - Aug 2021 (9 comments) Lisping at JPL (2002) - https://news.ycombinator.com/item?id=22087419 https://news.ycombinator.com/item?id=22087419 - Jan 2020 (307 comments) Lisping at JPL (2002) - https://news.ycombinator.com/item?id=13626074 https://news.ycombinator.com/item?id=13626074 - Feb 2017 (37 comments) Lisping at JPL (2002) - https://news.ycombinator.com/item?id=7989328 https://news.ycombinator.com/item?id=7989328 - July 2014 (19 comments) The rise and fall of Lisp at the Jet Propulsion Lab (2002) - https://news.ycombinator.com/item?id=2212211 https://news.ycombinator.com/item?id=2212211 - Feb 2011 (36 comments) The Rise and Fall of Lisp at the Jet Propulsion Lab. - https://news.ycombinator.com/item?id=304736 https://news.ycombinator.com/item?id=304736 - Sept 2008 (72 comments)
- lisper 4y ago> Updated last year I don't think so. What gave you that idea?
- nequo 4y agoThe author is Ron Garret. He was also interviewed last year on the CoRecursive podcast about the merits of Lisp at JPL, and the opposition to it. It’s worth listening to: https://www.corecursive.com/lisp-in-space-with-ron-garret/ https://www.corecursive.com/lisp-in-space-with-ron-garret/
- signaru 4y agoUnrelated, but I noticed the podcast's volume control applies the volume change on mouse release of the volume slider. It prevents adjusting the volume with audio feedback and you have to guess where the slider knob should be.
- mepian 4y agoHe is also here on HN: https://news.ycombinator.com/user?id=lisper https://news.ycombinator.com/user?id=lisper
- sillysaurusx 4y agoOh wow, I didn’t know lisper worked at JPL. Neat!
- lisper 4y ago20 years ago.
- deleted 4y ago[deleted]
- mepian 4y agoThis is blogspam, the original is still hosted here by the author himself: https://flownet.com/gat/jpl-lisp.html https://flownet.com/gat/jpl-lisp.html
- dang 4y agoOk, so the update from Aug 2022 is not by Ron? geez. Changed from https://mecrisp-stellaris-folkdoc.sourceforge.io/lisp.html https://mecrisp-stellaris-folkdoc.sourceforge.io/lisp.html now. Thanks!
- lisper 4y ago> Ok, so the update from Aug 2022 is not by Ron? Nope. Just a blatant copyright violation. (They even copied the copyright notice. That's cheeky.)
- spicybright 4y agoIs there any kind of browser extension that detects this sort of spam? I know that's a really tall order, but I'd love some kind of tool that tries to do something close to this, even if it's just a listing of other sites that have the same text with a button click.
- the_af 4y agoI saw that it was from sourceforge and never even bothered clicking so as to not give them traffic. Will the taint ever leave Sourceforge? I think not, they squandered any good will forever.
- sundarurfriend 4y agoWho is "they"? Afaik they're under new ownership that doesn't have anything to do with the past shady practices.
- jmclnx 4y ago> industry best practice To me that really means "industry best practice at commercial businesses". Moving to a different language because the new one is cool is a big wast of $
- comfypotato 4y agoI’m intrigued by the distinction between best practice and standard practice. Isn’t it standard because it’s the best? I can understand that non-standard practices might be best in niche situations, but this sounds like a discussion of “traditions are solutions to problems so old we’ve forgotten what they were”.
- aidenn0 4y agoPhillips head screws are pretty standard in the US, but pretty much any other non-slot screw head is technically superior (including at least two other plus shaped drivers I'm aware of). Most woodworkers I've known prefer a square shaped driver. Unless the costs of the screw significantly impact your margins, Phillips screws suck.
- serf 4y ago>Phillips screws suck. I felt this way through my entire engineering life until I bought a sailboat. Everything on marine stuff tends to be flat-head or similar design -- engaging a flat driver into a slot in a bumpy/roll-y ocean is hell. The self-centering engagement aspect of a cross-socket style drive is absolutely fantastic after a long day of trying to tighten flat-slot fastened tube-clamps and the like at sea during calm conditions, let alone during weather. That said -- yes, phillips head sucks, they round out and won't handle any decent amount of torque over repeated sessions without deformation. Robertson (square)/allen/torx kind of suck at sea, because they lack any form of self-centering without using special taper drivers. In a perfect world I think that I would like to use pozi-driv fasteners and drivers everywhere, but the reality is that there are so many types of specialty hardware in use in the marine-world that it would be difficult -- if not impossible -- to switch it all entirely over.
- aidenn0 4y agoYes, they are better than flathead screws, which are the second (or maybe third after a combination philips/flathead[1]) most common screw I encounter in daily use. 1: Which I just learned last month they make special screwdrivers for! https://www.amazon.com/Combo-Driver-4-Inch-Klein-Tools/dp/B00OJQWWFC https://www.amazon.com/Combo-Driver-4-Inch-Klein-Tools/dp/B0...
- travisgriggs 4y ago> The management world has tried to develop software engineering processes that allow people to be plugged into them like interchangeable components. I've wondered about this a lot lately. It's not limited to software engineering only, you see it in other creative/human domains as well. Media production. Teaching. So on. But it's made me wonder, why doesn't the equation ever invert: "The <fill_in_the_blank> world has tried to develop _management_ processes that allow people to be plugged into them like interchangeable components." Why has management never come under the scrutiny of "one size fits all" and the subsequent salary/headcount reduction?
- LarryMullins 4y agoAre you familiar with the concept of co-ops? A lot of businesses are run by their workers or their members/consumers. They can hire or fire people to work as management as they see fit. It's not very unlike the board of investors of a business hiring or firing management, except instead of a board of investors you have co-op members.
- travisgriggs 4y agoYeah, I love co-ops. I wish there were more of them. I'd love to work for one if the pay was acceptable.
- jimbokun 4y agoWould be interesting to structure a software startup as a coop. I think the pushback would be the founders and early employees willing to share equally with later employees/members.
- davidw 4y agoThere was one in my hometown, in a different industry. One thing I heard about it was that decision making was extremely painful.
- abadger9 4y agoMy mentor worked at JPL - he was a BS, MS, PhD from MIT - he got out of there so quick (i believe less than 2 years). He said the pace of work was so slow, he didn't feel like anything got done in his entire time there.
- ibrault 4y agoDepends on what you're working on and on if you're defining "getting stuff done" on a macro or micro scale. For large flagship missions, 2 years is nothing. The scale of work and level of verification required by these projects is massive and takes time. You've only got one shot to get things right with billions of dollars on the line, don't rush it.
- marmetio 4y agoHigh-assurance isn't really the culprit. It's more of a funding issue. If long NASA programs could save part of the first year's budget to use the second year, things would go a lot faster. You might get hired into an overstaffed team and not do that much for a year until it's crunch time and then you're underfunded so it takes an extra year. Arguably you spent three years to achieve one year's worth of accomplishments.
- dima55 4y agoYMMV. I'm a JPLer. We get plenty done.
- adastra22 4y agoYou ever worked in fast-paced startups before?
- gorgoiler 4y agoThis is a bit off topic but your comment reminded me of something I learned only comparatively recently: while these degrees are things we earn one at a time, they are sequential and the result is that your status (the degree to which you have climbed the academic ladder) does not accumulate, it only changes. So at one point in time your mentor would have held the status / degree / title of Bachelor of Science. They were then promoted to Master, and then to Doctor. That’s probably what you’re saying, and this isn’t really a correction. It’s simply something interesting that I wanted to share with everyone else.