cl21
Common Lisp in the 21st Century. (by cl21)
rutils
Radical Utilities for Common Lisp (by vseloved)
| cl21 | rutils | |
|---|---|---|
| 2 | 2 | |
| 901 | 245 | |
| 0.0% | - | |
| 0.0 | 0.0 | |
| almost 3 years ago | 5 days ago | |
| Common Lisp | Common Lisp | |
| The Unlicense | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cl21
Posts with mentions or reviews of cl21.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-02.
-
Emacs-like editors written in Common Lisp
> 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
-
Why are the makunbound functions fmakunbound, makunbound, and slot-makunbound named this way?
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).
rutils
Posts with mentions or reviews of rutils.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-02-06.
-
Why are the makunbound functions fmakunbound, makunbound, and slot-makunbound named this way?
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).
-
Lisp is Not an Acceptable Lisp
CL21 is pretty decent. I prefer rutils. Here's a list of the libraries I'd recommend to "modernize" CL:
What are some alternatives?
When comparing cl21 and rutils you can also consider the following projects:
drracket - DrRacket, IDE for Racket