The Lisp Spectrum

Lisp has a simple syntax that can be learned in a day. All code is written as expressions, known as S-Expressions, which are lists with prefix notation. The first element is the operator, and the rest are arguments.

(+ 1 2 3 4)
(list 1 2 (list 3 4))
(defun foo (a b c d) (+ a b c d))

The REPL is a major selling point for Lisp, allowing for interactive, incremental program development. This feature has influenced many modern languages to offer similar interactive experiences.

Lisp code has the same structure as lists, enabling the creation of macros with list-processing functions. This facilitates the development of Domain-Specific Languages (DSLs).

Emacs is the de facto standard for working with Lisps. This is due to the fact that it partly written and configurable with Emacs Lisp, another lisp dialect similar to Common Lisp. For every lisp you'll find an init.el file that you can use as an example for a quick setup to work with each lisp in Emacs out of the box. However there are some common packages that are worth mentioning here that will make your life much easier when working with lisps in Emacs:

We explore the different ways of installing every lisp such as:

• The availability of official packages in different package managers.
• Install from a script.
• Installing from source code.

We will also look into the first time setup for every lisp.

The availability of learning resources is crucial for any programming language. We will try to gather the most helpful resources for every lisp including:

• Documentation
• Books
• Videos
• Tutorials
• Community channels

Ease and speed of interacting with the REPL, including the possibility of connecting to a remote REPL.

While Emacs is the de facto standard for working with Lisps, some have their own IDEs (e.g., Dr. Racket for Racket) or support through plugins in other editors. We will explore available editor options for each Lisp.

• Tools for managing packages and projects.
• Ease of installing/uninstalling packages.
• Possibility of installing a specific version for a package.
• Package installation scopes (global, project-level, or both).

We will discuss the built-in libraries for each Lisp and their usability. Additionally, we will explore the ecosystem for each Lisp, including where to find and download packages.

This is very subjective as every lisp compiles to a different target(s). So, it's hard to decide whether the comparison of performance is between the lisp implementations or the target platforms.

Most lisps offer a way of interoperability with their target platform(s) or with other platforms as well. This can differ from one lisp to another, so this won't be a comparison but rather exploring the different options.