cl21 VS Kawa

> And Lisp is almost uniquely able to handle transitions to later standards as I described above. You don't actually have to forfeit backwards compatibility entirely or at all if the changes are handled by moving to a new default base package. :cl-user/:cl become :cl##-user/:cl##

Go use cl21[0] if you care for this sort of thing.

> more generic functions would open up more interesting developments later

generic-cl[1]. But in a prefix-oriented language, I just don't see this as particularly important.

> you don't necessarily want to bless a particular concurrency model

You do[2]; this is one of the notable deficiencies in the cl standard that really bites, today. It is being worked on.

0. http://cl21.org/

1. https://github.com/alex-gutev/generic-cl

2. https://www.hpl.hp.com/techreports/2004/HPL-2004-209.pdf

Dropping the idea for a new CL standard, adding these to CL21 would be the next option (I don't think such changes fit the spirit of radical-utilities).

Kawa (like Clojure) runs on the JavaVM, but has a longer pedigree (from 1996), good compatibility with standard Scehemes (including R7RS), and has a stronger emphasis on performance: It has optional types and semi-decent type inferance so it is easy to write code as performant as Java. It also has fast startup, and is unopinonated on how you run and bundle applications: it generates pretty vanilla class files that interoperate with Java easily. See https://www.gnu.org/software/org and https://gitlab.com/kashell/Kawa

Kawa is quite relevant, and it seems that the project started in 1996. Still actively maintained.