News for hackers. Stuff that matters.
Re:Steel Bank Common Lisp version 2.6.7 by epolanski on Tuesday July 28, 2026 @03:18PM (#49088605)
Lisp's been around for 70 years at this point and hordes of developers tried it and said: lovely, but I ain't using it at work.

I'm strongly convinced, having used Scheme, CL, Racket, Clojure that Lisp is doomed to be (mostly) a hobby language.

The very power of Lisp, macros, dynamic programming, reflection lead to a mess of an ecosystem where every single developer reinvents the wheel and nobody can understand yet another DSL invented by the next developer next to them.

Racket's theme of being a "programming language for building programming languages" is just the poster child of this naivety: I don't want even more friction.

What scales and works is simple and boring.

That's by the way why also Haskell has struggled forever. Beyond its dreadful DX, poor tooling and unacceptable compilation times, the language is just plagued by compiler extensions and every single developer reinventing its own abstractions.

There was the simple haskell movement to just standardize around a set of extensions and conventions, but nope, these languages unavoidably attract people that want to stay in the ivory tower.

Really, I love both lisps and haskell, but I would take a dreadful php over them every single day at work. No contest.

Re:Steel Bank Common Lisp version 2.6.7 by ux266478 on Tuesday July 28, 2026 @03:57PM (#49089098)
The problem is that the type of developer you're talking about is the type who just invents a thousand excuses about anything. It doesn't begin and end with different languages. Using a different subset of their favorite language? A different toolchain? A radically different build process? You'll hear plenty of whining about it. You put a Lisp or a Prolog in front of them, and their attention flows upwards to the most general principles to whine about. The entire thing is that if you stick them into an unfamiliar environment, they will vocalize their discomfort through rationalization. I think most people who have led teams will know exactly what I'm talking about.

Not that these people are necessarily bad at their jobs, but they're definitely a personality type you should learn to identify so you can manage them properly.

Re:Steel Bank Common Lisp version 2.6.7 by epolanski on Tuesday July 28, 2026 @04:43PM (#49089670)
Yes, that kind of developer exists everywhere, but is still limited by the tools you reign in him.

> I think most people who have led teams will know exactly what I'm talking about.

I've had those as leads themselves, with great benefit and pain. They further convinced me about the beauty of ugly and boring.

[dead]
Re:Steel Bank Common Lisp version 2.6.7 by anthk on Wednesday July 29, 2026 @06:07PM (#49103712)
> Lisp culture genuinely prizes getting-shit-done attitude.

SICP tells me otherwise.

Re:Steel Bank Common Lisp version 2.6.7 by vincent-manis on Wednesday July 29, 2026 @06:22PM (#49103864)
SICP is not intended as a how-to-program manual, it attempts to lay the foundation for a big chunk of computer science. “How To Design Programs” might be a better choice for someone learning Scheme. (But SICP will turn some of the people on to CS as a discipline.)
Re:Steel Bank Common Lisp version 2.6.7 by Jach on Wednesday July 29, 2026 @07:03PM (#49104221)
SICP, as beautiful and good as it is, is probably responsible for a large amount of the misconceptions and negative thoughts about Lisp. SICP isn't a Lisp book, it's a Scheme book, and the Scheme culture is at least as different to Lisp (Common Lisp and its ancestors all the way back to McCarthy) as Java is to Python.
Re:Steel Bank Common Lisp version 2.6.7 by anthk on Wednesday July 29, 2026 @07:26PM (#49104382)
I know both CL and Scheme, thanks. And both philosophies overlap a lot. Heck, there's an Scheme interpreter in PAIP as en exercise...

I'd woudn't consider SICP negative, the same with all the good CL books (Intro to Symbolic Computation, Paradigms of AI Programming...)

Both are the ur-examples on how to grasp the basic of CS well.

Re:Steel Bank Common Lisp version 2.6.7 by iLemming on Wednesday July 29, 2026 @07:15PM (#49104319)
Are you using a 42 year old book to find flaws in my argumentation? Let's talk real, contemporary numbers.

NuBank: from ~12M customers in 2019, grown to 25M in a year, then to 48M at IPO a year later, then to 114M in 2024, to 131M in 2025 - 991.67% growth within 6 years and still going. Not in theory, not conceptually, not because "SICP has told them". They did get-the-shit-done. Not acknowledging that Datomic and Clojure has something to do with this succes would be simply a dishonest gesture.

Walmart - the canonical "Clojure at scale" story. The eReceipts system processed every purchase across 5,000+ US stores plus online/mobile, built and maintained by just 8 developers. Architect Anthony Marcar's line after Black Friday: the system "handled its first Walmart Black Friday and came out without a scratch". They cited 5-10x less code than alternatives.

Apple - known for using Lisp for a long time.

Metabase - open-source BI. ~46k GitHub stars.

Amperity - customer data platform, "99% Clojure" - their own quote.

Netflix - been using Clojure since forever. Watch their talk from the last year's Conj. It's eye-opening on stability of complex systems.

Cisco - malware analysis platform. Multiple huge Clojure projects: IROH - Incident Response Orchestration Hub, CTIM/CTIA - Cisco Threat Intelligence Model and API, etc.

Braintree/PayPal - payments backend. CircleCI. Grammarly (this guys are on SBCL)

And that's just a short list of actual, real, profitable businesses built with and maintained using Lisp. I don't know what "SICP has told" you, but maybe you just need to look around, things have changed a bit since then.

Re:Steel Bank Common Lisp version 2.6.7 by anthk on Wednesday July 29, 2026 @07:25PM (#49104378)
I mean, both Scheme and CL have good libraries and a set of standards.
Re:Steel Bank Common Lisp version 2.6.7 by iLemming on Wednesday July 29, 2026 @07:48PM (#49104532)
Okay, but what that has to do with preferring strong CS theoretical grounds vs. cutting corners to get-the-shit-done?

My initial point was about cultures - Haskelites are typically very smart, extremely mathy, and they'd often choose certain ways even if it takes them forever and requires reading and analyzing dozens of academic papers, just because "Galois was a genius and we can make this theory fit here, because then we can center infinite divs on infinitely large DOM entities...", then publishes a paper "Coequalizers for Vertical Alignment: A Comonadic Approach"

A Lisper would be like: "Ahem... I wrapped the whole thing in a macro. Yes, it evals a string. Yes, the string is generated by another macro. No, I will not be explaining it. It shipped Tuesday, it prints money, it works. Gotta go, kids need dinner.."

Re:Steel Bank Common Lisp version 2.6.7 by anthk on Thursday July 30, 2026 @05:54AM (#49107857)
You forgot about HAKMEM under PDP10 assembly/ITS/MacLisp/Macsyma (these three/four ovelapped)
Re:Steel Bank Common Lisp version 2.6.7 by rootnod3 on Friday July 31, 2026 @11:54AM (#49124684)
So, Haskell people smart, other people dumb?

Also, where do you go from "preferring strong CS theoretical grounds" to "cutting corners"? They don't have to be mutually exclusive.

That garbage collection that Haskell has? Guess where that came from. The whole "functions as data to pass around", guess where that came from. It was those pesky lispers on a Tuesday.

Edit: typo

Re:Steel Bank Common Lisp version 2.6.7 by iLemming on Friday July 31, 2026 @04:54PM (#49128405)
> Haskell people smart, other people dumb?

Da hell you're talking about, friend? I said nothing about "people", or them being smart or dumb; just a difference in cultural stereotypes.

Now you're ironically "proving the point" I didn't make by saying some dumb shit and pulling me into this pit too. If I was actually smarter I'd probably just ignored it. Reminds me Billy Madison quote: "everyone in this room is now dumber for having listened to it. I award you no points, and may God have mercy on your soul."

Re:Steel Bank Common Lisp version 2.6.7 by anthk on Monday August 03, 2026 @02:01AM (#49151740)
>cultural stereotypes.

Again, check HAKMEM from ITS/Maclisp/PDP10's (The OS from Richard Stallman took all the ideas for GNU Emacs, the GPL license, the free software movemement and whatnot). Lisp itself accounts for tons of papers and innovation.

Re:Steel Bank Common Lisp version 2.6.7 by vincent-manis on Tuesday July 28, 2026 @03:44PM (#49088913)
I disagree with this profoundly. There is no argument that Lisp in general can get you in a terrible mess. So can C, or pretty much any language (I well remember a case of 11-way multiple inheritance in C++ game code). If I were running a Lisp-based project, there would be project standards (like no exported macros without signoff, and a list of standard library dependencies), documentation requirements, and code review.

The fact that Lisp is the “programmable programming language” doesn't mean that every engineer should be inventing weird versions of while loops. What it does mean is that a skilled Lisp programmer can build a domain-specific language that substantially helps in development.

One good example of this is the Crash Bandicoot games, along with the same studio's Jax and Daxter, which were built with dialects of Lisp (yes, they had to compile the code, and take care with storage allocation, just like any other game code). Cisco hired Kent Dybvig, principal author of the Chez Scheme system, and open-sourced that software; I have no clue what they use it for, to be honest, but I assume that they had some reason for doing this. Companies using various Lisp languages have been documented in areas from fintech to quantum computing.

Re:Steel Bank Common Lisp version 2.6.7 by rjsw on Tuesday July 28, 2026 @03:26PM (#49088715)
I use Common Lisp at work.
Re:Steel Bank Common Lisp version 2.6.7 by amboo7 on Tuesday July 28, 2026 @03:43PM (#49088904)
Me too
Re:Steel Bank Common Lisp version 2.6.7 by rootnod3 on Wednesday July 29, 2026 @12:45AM (#49093500)
Jealous of both of you
Re:Steel Bank Common Lisp version 2.6.7 by derrida on Wednesday July 29, 2026 @02:08AM (#49093932)
do you guys need a sweeper, janitor, someone to go fetch coffee or something?
Re:Steel Bank Common Lisp version 2.6.7 by oumua_don17 on Tuesday July 28, 2026 @03:30PM (#49088765)
>> said: lovely, but I ain't using it at work.

Says who, you? Wrong. I use Common Lisp at work.

edit: and not just use as in a side toy, design and writing software in CL is my primary responsibility. FWIW, at a FAANG!

Re:Steel Bank Common Lisp version 2.6.7 by stackghost on Tuesday July 28, 2026 @03:36PM (#49088832)
>FWIW, at a FAANG!

Do you work on ITA? Only FAANG I'm aware of using Lisp is Google.

Re:Steel Bank Common Lisp version 2.6.7 by oumua_don17 on Tuesday July 28, 2026 @03:45PM (#49088934)
Nope not on ITA. I work at the intersection of HW and SW. Lisp is valued for its strengths and I haven't come across any tool better to explore complex problem space. Of course, the opportunities are fewer, get filled up organically and are better suited for someone with valuable domain knowledge who can translate it into working space for a wider team using Lisp as the tool to write the spec!
Re:Steel Bank Common Lisp version 2.6.7 by stackghost on Tuesday July 28, 2026 @05:41PM (#49090306)
Sounds like a dream job, tbh
Re:Steel Bank Common Lisp version 2.6.7 by rootnod3 on Friday July 31, 2026 @02:55PM (#49127220)
You hiring? Sounds like a dream. Dead serious.
Re:Steel Bank Common Lisp version 2.6.7 by oumua_don17 on Thursday August 06, 2026 @07:14AM (#49195176)
Sorry, not hiring currently but rest assured I've bookmarked this comment and will reach out when we do.

I'm an IC and have three more engineers working alongside, so a very small team.

We don't expect anyone we're hiring to know, understand or have even heard of Lisp :-), just the curiosity and willingness (which we evaluated in the interviews) to grok it when provided enough support and runway to get upto speed.

As you seem to be keen for such a job, the best bet right now is start using SBCL in your daily work. Trick: don't say you're using Lisp just show (the output), don't tell!

Re:Steel Bank Common Lisp version 2.6.7 by michaelmrose on Tuesday July 28, 2026 @03:35PM (#49088821)
> The very power of Lisp, macros, dynamic programming, reflection lead to a mess of an ecosystem where every single developer reinvents the wheel and nobody can understand yet another DSL invented by the next developer next to them.

Have you like looked at anything in the Clojure ecosystem because this description makes no sense of any kind. Clojure has macros but less powerful than common lisp and Clojure code in the ecosystem tends to be small and understandable.

Re:Steel Bank Common Lisp version 2.6.7 by Zak on Tuesday July 28, 2026 @04:26PM (#49089481)
It seems to me the Clojure community internalized the lesson of not writing macros unless it's really necessary more than other Lisps did.
Re:Steel Bank Common Lisp version 2.6.7 by kscarlet on Tuesday July 28, 2026 @06:14PM (#49090689)
So does the community of every other dialect (Common Lisp, at least). Write a function if you don't have to write a macro, and maybe declaim the function to be inlined.

The "Lisp Curse" is a ridiculous and tired myth that can only be invented by people who have looked at the language for 5 seconds and went straight to finding an excuse to not learn it.

Re:Steel Bank Common Lisp version 2.6.7 by Zak on Tuesday July 28, 2026 @07:11PM (#49091248)
Is it? I saw macros and went mad with power. I wrote a macro that could have been a function today.

But seriously, I think Clojure has a particularly strong tradition of writing clean, readable code.

Re:Steel Bank Common Lisp version 2.6.7 by iLemming on Wednesday July 29, 2026 @10:14AM (#49097840)
Clojure is actually an interesting case here, because it is hosted. So, you can write a Clojurescript macro that runs at compile time on the JVM, but emits code that runs at runtime in Javascript, e.g. instead of blindly loading and executing some JS lib code, your macro can first parse it, analyze it, and conditionally emit Cljs that changes the runtime behavior.

Use-cases for code that writes code across a host boundary are rare, yet enormously useful and really difficult to achieve without homoiconic nature of the language.

Hyperfiddle/Electric is a nice project that effectively utilizes the idea.

Re:Steel Bank Common Lisp version 2.6.7 by p_l on Tuesday July 28, 2026 @05:32PM (#49090210)
I believe the real issue is that Scheme, which was (through university) often the first and last contact of people with Lisp family languages, has greatly exaggerated case of "everyone reinventing the wheel", and that's before you get into educational reasons that led to people seeing very limited view of Scheme
Re:Steel Bank Common Lisp version 2.6.7 by epolanski on Tuesday July 28, 2026 @04:45PM (#49089684)
Further confirming my point on why it is the only lisp with some genuine traction out there.
Re:Steel Bank Common Lisp version 2.6.7 by iLemming on Tuesday July 28, 2026 @06:24PM (#49090802)
I think you have very little insight to what you're talking about. The modern Lisp landscape is nothing like what it was in the 90s or even 2000s. The amount of practical shit Lispers been quietly building these days is genuinely impressive.

Have you ever seen GitHub language stats? Elisp there in the list a few points behind Lua, Elixir, OCaml and Haskell. The amount of Emacs Lisp on GitHub alone should be at least surprising. There's so much Elisp in the wild - the amount of it probably exceeds Clojure, CL and Racket combined. And let me remind you that it isn't a "general-purpose PL" - it's meant for one and only purpose.

Look at the number of package for AI-coding in Emacs¹ - 35 and counting. Mind that emacs has no central curated marketplace with the same discoverability as VSCode's. Packages live across MELPA, GNU/NonGNU ELPA, and countless personal repos, so a hand-counted 35 from a Reddit roundup is almost certainly an undercount of what exists in the wild.

And that's just one of the observable axes of Lisp. Anyone can join Clojurians Slack and scroll through #news-and-articles, just out of curiosity. It is hard to find a problem space today or a runtime where Lisp has not proliferated. Why? Because Lisp is enormously practical. Just because you convinced yourself it isn't, doesn't change a thing about reality.

---

¹ https://www.reddit.com/r/emacs/comments/1uwm3c0/the_state_of...

Re:Steel Bank Common Lisp version 2.6.7 by epolanski on Wednesday July 29, 2026 @05:40AM (#49095230)
It's mostly hobbyism.

My point stands.

Re:Steel Bank Common Lisp version 2.6.7 by iLemming on Wednesday July 29, 2026 @09:43AM (#49097434)
> My point stands.

Your point can stand, sit or jump around in a circle - makes no difference. Any ignorant fool can make a hollow point about things they don't fully understand and congratulate themselves in the process.

You can make similar "observation" about Linux on Desktop, mechanical keyboards, 3D printing and Raspberry Pi/Arduino tinkering and call them "hobby business".

You're essentially conflating "niche" with "unserious". By that logic Linux was a hobby OS and Git a hobby VCS - both literally started as one guy's side project, both now run the industry. Lisp is niche, not unserious: Clojure runs Nubank, Walmart, Cisco and Apple; Common Lisp ran ITA/Google Flights; and most of the features in whatever your favorite language is were Lisp ideas first.

Re:Steel Bank Common Lisp version 2.6.7 by offlineguy on Tuesday July 28, 2026 @05:02PM (#49089857)
I was fortunate enough to use lisp professionally for nearly 20 years. The only reason that gig ended was the unfortunate demise of the majority owner and founder, and his heirs selling the shop to a competitor that only wanted the customer database imported. Lisp was never the problem, nor particularily messy.

On the contrary, we considered it a major reason we were able to build a quite successful stock broker and bank from scratch with a team of 4-6 people, who doubled as datacenter ops (we ran on-prem), internal tech support for the rest of the firm (~20 people) and 2.line customer support.

We quite naturally converged on a set of internal libraries for various tasks. Understanding and fixing each other’s code was not a big deal.

Coincidentally, our frontend was php. That was messier, and we conciously kept that layer as lean as possible.

Re:Steel Bank Common Lisp version 2.6.7 by iLemming on Tuesday July 28, 2026 @05:50PM (#49090395)
I have a complete and utterly opposite experience. I have used and shipped all sorts of solutions in dozens of different languages before getting to know Lisp. My only regret is that I have not tried learning Lisp sooner - it feels like such a walloping waste of my life.

Lisp dialects turned out to be extremely practical - I just can't even imagine doing the things I do today with Emacs in anything else. Achieving similar effects with any other tool would be enormously more time consuming and far more frustrating. Sure, it really took me years to get to that point, but even though I had already knew all sorts of other tools which I could've picked to achieve similar results - from bash/zsh, awk, sed and tcl to python, golang and a bunch of others, the way Lisp-driven Emacs lets me get there is beyond meaningful comparison. Nothing even comes close and I'm enormously proficient in vim, I spent almost a decade in IntelliJ and used tons of different IDEs before - from Delphi and Eclipse to Visual Studio and VSCode.

Clojure, at which I scoffed at some point, turned out to be an immensely pragmatic tool for dealing with data. Any kind of data - big or small. It effectively replaced jq in my toolbelt, all my API interrogations happen in a Clojure REPL today. Fetching data from psql, mysql, sqlite and sorting, slicing, dicing, transforming that data interactively, directly from my editor is an absolute delight.

Building simple web-scraping scripts with nbb driving Playwright is so much faster than using any other stack, even javascript is no longer "an obvious choice" for me, even though I spent decades learning its quirks.

Babashka has replaced any kind of bash-scripting - anything longer than three lines almost has no reason to be made in bash/zsh/fish anymore.

Anything Lua-driven is now done with Fennel. It's not even funny how a dozen-lines boilerplate of Lua can be compacted into a simple, reasonable three-liner Fennel macro. Or the way how I can connect to the Hammerspoon REPL and poke through visual elements of any app on Mac, interactively and with ease - is complete and total bananas.

Era of LLMs incidentally highlighted another enormous advantage of Lisp - when you give an LLM a true Lisp REPL, agents stop guessing and start empirically analyzing current state of things and produces working solution faster, costing far less tokens. And you get to watch it solve things interactively, e.g. I often let AI poke through our UI (via Playwright-driven Clojurescript REPL), while monitoring situation in k8s - through nrepl port, connected to Clojure REPL. It literally interactively walks the DOM, finds the selectors, clicks buttons, etc. All without restarts, complex state management and all.

"Well", you may say: "these examples exactly what I'd consider a 'hobby language' territory".

Alas, I have worked in teams where Clojure was used for shipping commercial software and I have seen truly complex projects - Cisco's infosec infrastructure and FindingCircle's complex Kafka topologies. I have met and talked to people working at Netflix, Apple, Amazon, Nubank, CircleCI, etc., and I can confidently say: your self-conviction is absolutely backwards.

Lisp-world has never been more cornucopian than today; we see the proliferation of different tools and new Lisp dialects popping almost every passing week - Jank, Jolt, ClojureDart, Squint, Coalton, Clojerl, LFE, uLisp, etc. It is frankly inconceivable to find today any platform where you can't really run a Lisp. My advice to any programmer who's aspired to become a hacker - do learn Lisp. It comes in handy. For real.

Re:Steel Bank Common Lisp version 2.6.7 by mark_l_watson on Tuesday July 28, 2026 @06:43PM (#49090990)
+1 upvote

I don’t agree with you but your comment is very well thought out and doesn’t deserve downvotes.

Re:Steel Bank Common Lisp version 2.6.7 by derrida on Saturday August 01, 2026 @03:44AM (#49132096)
> Lisp is doomed to be (mostly) a hobby language.

Message Sent from Common Lisp