March 10, 2026

Lisp in a Box, Drama on the Rocks

Getting Started in Common Lisp

Plug‑and‑play Lisp arrives—fans cheer, skeptics ask “why bother in the LLM era”

TLDR: A one‑command, all‑in‑one Common Lisp setup promises painless onboarding, complete with editor and web visuals. The crowd is split: some say AI coding assistants make niche languages a dead end, while others celebrate a faster, distraction‑free Lisp workflow—sparking a classic Emacs‑vs‑IDE culture clash.

A new “batteries‑included” setup for Common Lisp just dropped, promising a zero‑fuss start: run one command, open Emacs, and boom—code, plots, and a web page on your laptop. It bundles the editor, add‑ons, and even a mini server so you can see graphs in your browser. But the real action is in the comments, where the crowd immediately split into camps.

One side went full doomer: an early zinger joked that in the age of AI coding assistants, picking a niche language is self‑sabotage—“that’s the neat thing: you don’t” get started. Others countered with pure old‑school energy, praising the Emacs+SLIME combo (a text editor plus a live coding console) for putting them in a flow state faster than any “bloated, distracting” modern IDE. The Vim crew showed up too, waving vim‑slime like a rally flag.

Veterans reminisced—and vented. One longtime Lisper said Go’s library ecosystem left Lisp in the dust, so they built a bridge to use Go packages from Lisp. Another lamented the dream of a live, all‑in‑one system that spits out tiny production apps—“it never came”—and even Smalltalk wasn’t the answer.

Bottom line: the new image makes Lisp friendlier than it’s been in years, but the comments turned it into a culture war—AI pragmatists vs. REPL romantics, with plenty of snark to go around.

Key Points

  • A preconfigured OCI image, ls-dev, is introduced to simplify Common Lisp and Lisp-Stat development.
  • The image includes Emacs, SLIME, Quicklisp, Lisp-Stat, and sample datasets/plots.
  • Users can start with a single Docker command pulling ghcr.io/lisp-stat/ls-dev:latest, then run Emacs and M-x slime.
  • An ls-server starts automatically on port 20202, offering a web interface for plots and data-frame editing at https://localhost:20202.
  • A refresh script keeps the environment synced with upstream Lisp-Stat; the image supports general Common Lisp development and invites contributions/bug reports.

Hottest takes

“That’s the neat thing—you don’t.” — bitwize
“They are slow, bloated and distracting.” — ukkare
“People recommend Smalltalk for this but that’s not a Lisp.” — jonathanstrange
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.