clisp VS tungsten

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.

But no one is stopping you from building a "full modern standard library". I am doing just that with https://github.com/galdor/tungsten. Of course it would be nice to have a large company do all the work as it is the case for Go, but it is not going to happen. As always, you either do the work yourself or pay someone to do it.

The specification is limited, no doubt about that, but I am convinced that any modernization effort would end up in a huge mess with everyone trying to inject their own preferences from the languages they already know with no regard for the spirit of the original specification.