Common Lisp Development Tooling — Reference Card


Map of the Common Lisp Dev Stack

This is the concise reference map on Lisp Development Tooling. Find the full article here — it’s 6,000 words so not for the faint hearted, but worth it if you prefer deeper explanations.


Legend


LayerToolWhat it is
6EmacsExtensible editor. Primary CL dev environment via SLIME or SLY.
LemEditor written in Common Lisp. Built-in SWANK support, no config needed.
VSCode + AliveVSCode extension for CL development. Least mature integration.
Pulsar + SLIMAAtom successor with SWANK integration.
Vim/NeovimVia Vlime, Nvlime, or SLIMV.
5aSWANKServer-side protocol. Runs inside the Lisp image, exposes debugger/inspector/completion.
SLYNKSLY’s fork of SWANK. Same role, paired with the SLY client.
5bSLIMESuperior Lisp Interaction Mode for Emacs. Original SWANK client. Gold standard.
SLYModern SLIME fork. Flex completion, stickers, cleaner internals. Default in Doom Emacs.
4QlotPer-project dependency isolation. qlfile/lockfile model. Most widely adopted.
CLPMCL Project Manager. Cleanest architecture, separates resolver from runtime.
ociclOCI-based package distribution. Handles both Layer 3 and Layer 4.
vendVendors dependency source directly into project. Replaces Layers 3+4.
3QuicklispCentral library repository. Monthly curated releases. The default.
UltralispSupplementary distribution. Updates more frequently than Quicklisp.
2ASDFAnother System Definition Facility. Build system. Bundled with all modern CL compilers.
1SBCLSteel Bank Common Lisp. Most popular open-source compiler. Native code.
CCLClozure Common Lisp. Fast compilation, macOS-friendly.
ECLEmbeddable Common Lisp. Compiles via C, good for embedding.
ABCLArmed Bear Common Lisp. Runs on the JVM.
CLISPGNU CLISP. Bytecode interpreter. Useful for bootstrapping SBCL from source.
*RoswellCL implementation manager and launcher. Manages Layers 1-3 from a single tool.
*LispWorksCommercial CL environment. Collapses all layers into one integrated product.
*Allegro CLCommercial CL from Franz Inc. Full IDE, profiler, support contracts.

Notes:

  • A most highly recommended resource is the Common Lisp Cookbook.

  • Steve Losh’s blog has some very readable articles on Lisp.

  • Checkout r/lisp and r/Common_Lisp for good people with lots of helpful advice.

  • While commercial Lisp environments aren’t covered in depth here they are worth looking into.

*Community contributions from r/lisp, r/Common_Lisp and Hacker News acknowledged in the full article.