zachbeane

Common Lisp at its base is usually written in Common Lisp.

The class and instance evolution protocols for starters seem not all that easy.

If you mean the C compiled code, that's what a typical sbcl binary is already. On my system it's around 2.5MB. The compiled CL code image (and its related data) is around 50MB. save-lisp-and-die sticks the image into the runtime binary.

It extends to Topsfield. At the intersection of Route 1 and Route 6 there's a model of Eris.

The Mark Zuckerberg profile is promoted heavily on "who to follow"-type interstitials. It also shows up when friends like or share things it posts. Blocking would be a simple way to avoid seeing those things, if it worked.

I hope to improve the documentation and security of Quicklisp in the next few months. It will depend on funding.

The core of Quicklisp is in dist.lisp. Understanding the protocol of the generic functions at the start of that file will help clarify Quicklisp as a whole. Almost everything else Quicklisp does is in support of that protocol.

This is a not a good guide. Avoid Graham too.

PCL is much better. Keene too. Seek out Joe Marshall's Warp Speed intro too.

Postmodern is good. It works only on Postgres. It is fast, easy, and stable.

Elephant has been unmaintained for many years. I wouldn't recommend it.

GNU CLISP does not get any resources, human or otherwise, from the GNU project. If Sam stops working on CLISP, he's not going to start working on GNU Emacs or gdb instead.

This is true in the same sense that the GIMP is the "GNU Image Manipulation Program". It's just a label, and a license choice, without much real meaning behind it. GCL is also called "GNU Common Lisp".

CMUCL is not popular any more.

SBCL is popular, and so is Clozure CL.