4 ms·
Every once in a while, there's a post on front page HN about Haskell and/or Lisp. Sometimes these posts get a lot of traction, but what confuses me is despite t
by behnamoh 6y ago
Every once in a while, there's a post on front page HN about Haskell and/or Lisp. Sometimes these posts get a lot of traction, but what confuses me is despite the apparent popularity of these languages among developers, still they are seldom used in serious software. I know there are exceptions (esp. with regards to Lisp), but still these languages never come close to other languages such as Java, JS, C, or even Scala.
- thom 6y agoMost tech companies are (quite rightly) in the business of managing imperfections, not achieving perfection.
- sullyj3 6y agoCombination of somewhat high barrier to entry (they're unlike most other languages so experience isn't as transferable), and network effects - those in charge of choosing a technology for a project generally make the subjectively prudent decision to use technology that is already in common use, leaving the less common languages in a catch 22.
- rainsil 6y agoI doubt this explanation really captures the gist of the phenomenon. Many current and upcoming trends (containers/Kubernetes, machine learning and Rust, for instance) have suffered in varying degrees from either of those problems, yet their adoption among companies is ever-increasing. I suspect they suffer from an issue also shared by the likes of cryptocurrencies: they don't have a "killer benefit"; a concise, persuasive reason that using them is a discrete improvement over current practice (like "high-level systems programming!", or "self-driving cars!").
- dunefox 6y ago> still they are seldom used in serious software This is mostly because the majority of software developers only know Java and are averse to learning new languages. Also, companies chose Java at one point and are now taking next to no risks by introducing new languages (not even languages on the JVM). They can also just fire and rehire Java developers because there is a large pool of available developers that they can just plug-n-play, so to speak. They're not interested training people.
- pyrale 6y agoAs a paid user of haskell and Java, here are a few of the things I experienced when discussing about language choices in corporate settings: * Fail a project in Java, and you have a project failure. Fail a project in Haskell, and you have a Haskell failure. * Management has a large veto power, and management usually favors technologies they are used to, or used to use themselves. * Management also favors their ease of work with the tech. In practice, they often hold the belief that it's much easier to find java developers than it is to find haskell developers. * Haskell suffers from a reputation of being "academic" and "hard to do real things with". In practice, I've done great commercial projects in Haskell, and the technology was worth using. When done right, recruiting for haskell projects was much faster than recruiting for any mainstream language. On the flipside, it was sometimes hard to get adequate corporate stewardship for the language (for instance, managers/HR insisting they found no one for the job after publishing through the usual channels when you know half a dozen people at the local meetup that would jump ship if offered a position).
- rjsw 6y agoI'm writing serious software in Lisp. Other developers working in related areas are using Ruby and Python but my software runs a lot faster.
- z3phyr 6y agoJust wait for symbolic computers to be rediscovered and the industry will probably adopt lisp and prolog's successors.
- dunefox 6y agoOne can dream.
- guenthert 6y agoThat has been discussed to death already. Common Lisp might be a niche, but it appears to be even more of a niche than it actually is when cursory looking at major projects. Common Lisp (and similar languages) are (particularly, not only) well suited for prototypes created by a small group of well interacting developers. If you shoot for very large systems, with a very large staff of various talent and experience (and inevitable communication break-downs), then e.g. Java is the safer bet. For this reason, rewriting a Common Lisp program into Java is not a sign of failure of the language, but a sign of success of the project.
- vindarel 6y agoOld and recent companies using Lisp: https://common-lisp.net/lisp-companies https://common-lisp.net/lisp-companies Includes Google (ITA Software, still powering airfare search engines), Boeing, Nasa (remember that Lisp was sent to space), Grammarly, OpusModus, Rigetti (Quantum computing), SISCOG (running metropilatan in european capitals), Ravenpack (big data analysis for financial services), PostgreSQL (pgloader), the ACL2 internationally-used theorem prover, etc
- veddox 6y agoYou have to remember that HN users aren't a representative subset of software developers world-wide. Part of that may be the continuing influence of PG: I both learnt Lisp and found HN because of his essays, and I suspect I'm not the only one. But also, the HN community generally has an academic fondness for new and niche languages, so a language's popularity on HN is a poor proxy for its popularity in the business world. (A last point: I think the diminished importance of Lisp in the last decades is less due to an inherent flaw of the language and more to what you might call "accidents of history" - particularly its close association with early attempts at AI.)