clisp VS npt

One should note that while it is true that the last CLISP release was a long time ago and there is not a lot of development going on right now, it's not dead. Bruno Haible just commited last week.

The repository is now at https://gitlab.com/gnu-clisp/clisp

CLISP is maintained here: https://gitlab.com/gnu-clisp/clisp/-/commits/master

Roswell has switched its clisp-head to be built from https://github.com/roswell/clisp/ which is based on the commits from CLISP's canonical repository along with patches which add package-local nicknames to it.

Oh dang, there is new development on clisp! I had to do some digging to find [the repo](https://gitlab.com/gnu-clisp/clisp), but it looks like the latest commit even adds support for MacOS on ARM.

> phoe got package local nicknames into all implementations

Unfortunately it's not yet in Clisp. I submitted a merge request[1] a year ago, but it's been silent since then.

[1]: https://gitlab.com/gnu-clisp/clisp/-/merge_requests/3

Quick note, CLISP is actually an implementation of Common Lisp, and as such isn't used as an abbreviation for Common Lisp the language. Could you expand on what you mean w.r.t to package managers? As far as getting up and running with a CL environment, Portacle makes this pretty easy now.

No love for NPT (<https://github.com/nptcl/npt>)? Well, I get it, it is very, very new.

One note about ABCL is that it doesn't support TCO, which the Common Lisp spec doesn't mandate. For people who want a Lisp on the JVM and really want tail calls, I would recommend checking out Kawa (<https://www.gnu.org/software/kawa/index.html>).

based on the conversation on IRC it is npt: https://github.com/nptcl/npt