Common Lisp Development Tooling — Reference Card

Legend


Layer Tool What it is
6 Emacs Extensible editor. Primary CL dev environment via SLIME or SLY.
Lem Editor written in Common Lisp. Built-in SWANK support, no config needed.
VSCode + Alive VSCode extension for CL development. Least mature integration.
Pulsar + SLIMA Atom successor with SWANK integration.
Vim/Neovim Via Vlime, Nvlime, or SLIMV.
5a SWANK Server-side protocol. Runs inside the Lisp image, exposes debugger/inspector/completion.
SLYNK SLY’s fork of SWANK. Same role, paired with the SLY client.
5b SLIME Superior Lisp Interaction Mode for Emacs. Original SWANK client. Gold standard.
SLY Modern SLIME fork. Flex completion, stickers, cleaner internals. Default in Doom Emacs.
4 Qlot Per-project dependency isolation. qlfile/lockfile model. Most widely adopted.
CLPM CL Project Manager. Cleanest architecture, separates resolver from runtime.
ocicl OCI-based package distribution. Handles both Layer 3 and Layer 4.
vend Vendors dependency source directly into project. Replaces Layers 3+4.
3 Quicklisp Central library repository. Monthly curated releases. The default.
Ultralisp Supplementary distribution. Updates more frequently than Quicklisp.
2 ASDF Another System Definition Facility. Build system. Bundled with all modern CL compilers.
1 SBCL Steel Bank Common Lisp. Most popular open-source compiler. Native code.
CCL Clozure Common Lisp. Fast compilation, macOS-friendly.
ECL Embeddable Common Lisp. Compiles via C, good for embedding.
ABCL Armed Bear Common Lisp. Runs on the JVM.
CLISP GNU CLISP. Bytecode interpreter. Useful for bootstrapping SBCL from source.
* Roswell CL implementation manager and launcher. Manages Layers 1-3 from a single tool.
* LispWorks Commercial CL environment. Collapses all layers into one integrated product.
* Allegro CL Commercial 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.