Picking Your First Lisp: Why the Dialect Matters Less Than You Think

Unlike most languages, which stay a single language across implementations, Lisp is a family with more than 20 living dialects that share a core syntax but diverge in operators, semantics, and standard libraries. This first entry in a series argues that beginners over-worry the choice of dialect. The real skill is learning to think in Lisp; concepts transfer easily once you know one, so any actively maintained dialect is a fine starting point.

The bulk of the piece profiles Common Lisp, the oldest and most feature-complete member of the family. Standardized as ANSI CL in 1994, it remains stable enough that code from books like Norvig’s 1991 PAIP still runs today, sparing developers the backward-incompatibility churn familiar to Python and Ruby users. Its flagship implementation SBCL compiles to native code with performance rivaling C and Rust. Standout capabilities include a condition-and-restart system for live debugging against a running process, a deeply integrated REPL that can attach to remote servers, and CLOS, an object system with multiple dispatch and generic functions that outclasses Java or C++. The trade-offs: no corporate backing, a small volunteer community, patchy documentation, and missing modern conveniences like persistent immutable collections, lazy sequences, and built-in pattern matching.

The author makes the practical case that CL excels at research, prototyping, and startups where requirements shift constantly, citing real users like Rigetti (quantum computing), Grammarly, and Google Flight Search, plus the Steam game Kandria. A notable aside: Hacker News itself, originally written in Paul Graham’s Arc dialect, now runs on Clarc atop SBCL, serving roughly 10 million pages a day. The post closes with recommended learning resources including Practical Common Lisp, Land of Lisp, and On Lisp, and endorses Emacs with Sly/Slime for tooling.