6 ms·
Even today, Common Lisp is still one of the best choices for many applications. Then why don't people build amazing and popular things with it? I don't mean on
by jodrellblank 10y ago
Even today, Common Lisp is still one of the best choices for many applications.
Then why don't people build amazing and popular things with it? I don't mean one or two people build one or two things, but lots of people building lots of things.
Nobody uses it, but it's the best choice, can't both be true. And 'nobody uses it' is approximately true. It's not a mainstream JVM language or CLR language, it's not an AWS or Azure or Google Web Services language, it's not used for Linux Kernel, Windows, Oracle, *BSD, SQL databases, No-SQL databases, it's not used where Erlang is, it's not the research language Haskell is, it's not the fun esolang or the long-tail COBOL, it's not the new compiles-to-JavaScript, it's not the back of 3D games or VR engines, it's not behind Amazon's shop or used where Go is. It's not talked about in StackOverflow's most popular languages surveys, or most profitable languages for devs to learn, or most desired by employers. It's not an educational language like it once was.
Yet it's "one of the best choices".
I simply don't believe it. Any perceived advantages it has, in practise must be a wash.
- nostrademons 10y agoToo much fun to program in. Lisp makes it remarkably easy to extend the language into just what you want it to be...which means that Lisp programmers tend to spend most of their time extending the language into just what they want it to be rather than solving the problem. (Indeed, this is often touted as one of the benefits of Lisp...once you have a suitably well-adapted DSL, the problem solution follows naturally.) Meanwhile, the Java or Go programmer is thinking "this is boring and ugly. Let me finish this problem as quickly as I can so I can go home." So they finish the problem as quickly as they can, and then it's done, and it ships. And people have an incentive to use it rather than tinker with it because nobody really wants to peek under the hood, and the people who do peek under the hood tend to be really dedicated and care a lot about the problem domain because why else would you put up with the language?
- jodrellblank 10y agoThis one I can believe.
- onion2k 10y agoThen why don't people build amazing and popular things with it? The reason is because "best" can have more than one meaning. Languages are usually only "best" at one thing, not for all things. In the case of many languages that people consider to be "best", they've been optimised for the development process (making it nice to write code in) rather than speed (C) or security (Ada) or a specific niche (R) or maintainability (not sure) or customisability (LISP). They're designed to make writing code more straightforward. Languages that are optimised to be easy to code with are the languages that tend to bubble up to the top when it comes to popularity contests because the more people who can access the language the more popular it's going to be. There is an argument that Ruby is mostly LISP, so it could be said that lots of people use it very happily everyday.
- vishbar 10y ago> There is an argument that Ruby is mostly LISP, so it could be said that lots of people use it very happily everyday. How is that? I thought Lisp's "killer app" was its extremely powerful macroing system. Does Ruby have an equivalent?
- onion2k 10y agoIt has class level declarations which do the same thing.
- jodrellblank 10y agoI would go with that, in the sense that "here's a box of parts" is the most customisable way to solve a problem - yet not the best way for most people. Except, even people doing exploratory stuff apparently aren't using Common-LISP. Let me point to Slava from RethinkDB, who wrote blogs about how amazing LISP is and then went to found a new-software startup written in C++. Peter Norvig, AI researcher, who moved from LISP to Python. And even your mention of Ruby - "Common LISP is the best langauge", then why is Ruby even needed? Why aren't those people happily using Common LISP? Simply because it wasn't actually any better, and was in fact worse than Ruby in whatever metrics.
- reikonomusha 10y agoA few notes: * Google actively develops one of the Lisp compilers. Google Flights powers Orbitz, Kayak, etc. That's Lisp. * There are several Lisp compilers in active open source development. * There's a graph database written in Lisp called AllegroCache. It's good enough to support a business (Franz) for more than a decade. * Another company (LispWorks) also exists and has a large portfolio of clients. * Lisp has been used to make entire operating systems. Ones of the past, and ones of now. (Of course, an OS needs a community. But where are real OS's with GUIs in other languages?) * Lisp has been successfully used in my own career for embedded systems to control satellite acquisition systems to, most recently, quantum computing. (At real companies.) Just because there's not this huge buzz around Lisp doesn't mean no one is using it.
- jpatokal 10y agoI don't even code in Lisp, but I knew the Google Flights engine would come up, because it seems to be just about the only "serious" application ever written in Lisp. And it wasn't built by Google, but their acquisition ITA, which hails from Boston and MIT's Scheme reality distortion field. (And even MIT has stopped teaching SICP in Scheme...)
- lisper 10y agoEmacs, ViaWeb, Macsyma, the DS1 Remote Agent, much of the autonomous navigation software for the Mars Rover before the Pathfinder mission... And I have built a number of small-scale web applications in Common Lisp. I'm running one of them in production right now.
- jodrellblank 10y agoAnd Yahoo! paid 49 million dollars of stock to throw the LISP in the trash and use something else instead. It wasn't even worth them spending 1 million dollars - 2% of that price - on training people. http://discuss.fogcreek.com/joelonsoftware/default.asp?cmd=show&ixPost=31402 http://discuss.fogcreek.com/joelonsoftware/default.asp?cmd=s...
- lisper 10y agoSure, in practice people's beliefs about languages can become self-fulfilling prophecies. And the thing about self-fulfilling prophecies is that they are actually true. For example, Javascript is tremendously useful even thought it is a horrible language from a technical point of view, it's just that the sheer weight of people using it because everyone else is using it results in enough infrastructure that you can get useful things done in in Javascript despite its (lack of) technical merits, not because of them.
- jodrellblank 10y agoAnd when JavaScript was becoming a thing, where was the better alternative written in LISP and the community of people who like better software supporting it? Nowhere, that's where. Like in approximately all problem domains, whatever perceived benefits LISP has, doesn't seem to make it all that desirable.
- dragandj 10y agoYou are writing this comment in the lisp-based software. Yeah, I know, Hacker news is a simple software and could have been written in anything else, but, somehow, the author, who I've heard is very smart, thought that Lisp is the best pick.
- jodrellblank 10y agoAnd his secret to winning big was "write lisp software, have it bought out by another company who will rewrite it in a different language to make it popular and useful". Really, if PG's "LISP, how to win big" was as compelling and important as he tried to state in that essay, every ycombinator company would be using LISP for their secret advantage over other companies. Applicants would choose LISP because it's "better", LISP-based applications would be preferred because the applicants have an advantage, existing companies would be encouraged to LISP because it would help them do more for less employee numbers and YC would become a LISPy community of alumni. I have no proof that this is not happening right now, but would you bet on it happening right now in secret?
- dragandj 10y agoYour logic assumes that young founders/developers are very proficient in many languages (including lisp) and they have perfect information for choosing. In reality, they use whatever crap they picked up hacking in high school. On top of that, the tools are only a part of the ingredients. However bad your platform is, at least it works, while most of the screw-up is hidden in business decisions - that's why every startup incubator's job is to help the youngsters not screw up business-wise. Tech is normally something up to the founders, most of whom have never heard of lisp.
- tmerr 10y ago>Nobody uses it, but it's the best choice, both can't be true Sure it can. It is possible for both to be true, as long as developers don't pick languages rationally, which they probably don't. There are a few biases at play. One is that people are only exposed to a subset of the languages that exist, which are those that are either used in industry, or are making the rounds in news. Another bias is that we like to pick languages based on familiarity. For example most of my college courses used imperative languages: Python, C++, and Java. From that experience I am quicker at thinking in terms of for loops than folds and maps. So when I try a language like Haskell or LISPs I think "That's neat!" but when faced with a deadline I switch back to something closer to my first languages. It could be that I am the only one that thinks like this, and everyone else sits down and spends equal time on every language in existence, but I doubt it. In any case at one point LISPs were popular, so why did they lose all of their momentum?
- jodrellblank 10y agoI also doubt it. But LISP dates back to 1958. JavaScript is from 1995. "I chose the language which exists" doesn't apply to the people in 1994 who could have had /thirty-five years/ of LISP experience (potentially) and yet still chose to write another language, in another language. And when Brendan Eich was in college around 1981, the tutors there could have had /twenty years/ of LISP experience, but weren't there to convince him that it was amazing. Same with literally any language dating post-LISP, and I note that that covers most languages which are popular today. "Programmers don't pick rationally" is fine on the small scale, but accross the entire industry, even among people who do love exploring programming languages, even among young entrepreneurial risk takers, even among companies in tough markets angling for any and every edge they can get over their competitors, in decade after decade, over problem domain after problem domain after problem domain, there is this empty howling wasteland of happy and productive people using not-LISP, writing world-conquering systems that do just-fine-thanks and the claimed benefits of LISP just don't seem to be making any noticable dent in anything. Therefore, they are over-hyped.
- lisper 10y agoYou are overlooking a crucial fact: very often people who want to use Lisp are not allowed to by their management precisely because "no one uses it" and so the experiment never gets done. I was the lead engineer on the first release of AdWords. I wanted to write it in Lisp, but I was not allowed to, being forced against my strenuous objections to to it in Java. So now AdWords is a Java success story rather than the Lisp success story it might have been not because Java is better (it certainly wasn't -- it was a disaster) but because my boss issued an edict. This has happened to me many times in my career. The one time I was actually allowed to use Lisp in a project that I did not have direct control over (the DS1 remote agent) it was an overwhelming technical success. In fact, management tried and failed to get the software rewritten in C++, so this was actually a controlled experiment.
- jcadam 10y agoPlease. You pick a lowest-common-denominator language like Java or Golang so that you have a large pool of cheap, semi-sentient code monkeys to hire from. If you choose LISP, you're actually going to have to expend a little bit of effort on identifying, recruiting, and retaining actually competent people. That's a problem when you're looking to put butts-in-seats (as is the case in my industry: defense).
- jodrellblank 10y agoThat just pushes the problem back a couple of decades. Common-LISP is from 1984, GoLang is from 2007. In twenty years, Common-LISP with all the advantage it supposedly has couldn't make anything that a 'code monkey' could use? Why not? Is it awful at writing tools? Or is it that the alledged advantages of Common-LISP don't really make any difference in reality because they are over-hyped or even non-existent? Note that I'm not saying "why did they pick one language over another", I'm saying "Common LISP can be the best tool for the job - yet they waited twenty years to use a 'worse' tool to implement a 'worse' tool". That doesn't make sense.
- lispm 10y ago> Nobody uses it This application is written in 7+ million lines of Common Lisp https://www.ptc.com/cad/elements-direct/modeling https://www.ptc.com/cad/elements-direct/modeling https://www.youtube.com/watch?v=mJGytRaNvec https://www.youtube.com/watch?v=mJGytRaNvec The video shows how Eterna uses 'PTC Creo Elements/Direct' to develop their watches. There are many other clients of that in various domains. Also: https://www.youtube.com/watch?v=4rD0zmA-Trc https://www.youtube.com/watch?v=4rD0zmA-Trc
- jodrellblank 10y agoGood cite. (Although the fact that some people can make successful Common LISP software could just be that those people are exceptional enough to make successful software in any language, it doesn't bolster the claim that 'Common LISP is one of the best choices for many applications' very strongly).
- lispm 10y agoInmarsat uses a Lisp application (G2) to monitor their satellites and to provide a high level overview of the status of all Inmarsat services in real-time. http://www.inmarsat.com http://www.inmarsat.com If you would run a Cement plant, an oil pipeline or a coal terminal in South Africa, then you might also be using G2 to control and diagnose technical processes in real-time. The product used, written in Lisp: http://www.gensym.com/wp-content/uploads/Gensym-l-G2.pdf http://www.gensym.com/wp-content/uploads/Gensym-l-G2.pdf