Cl21 Alternatives

Similar projects and alternatives to cl21

Fennel

90 2,281 9.1 Fennel cl21 VS Fennel

Lua Lisp Language
Carp

84 5,393 0.7 Haskell cl21 VS Carp

A statically typed lisp, without a GC, for real-time applications.
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
lem

55 2,048 9.9 Common Lisp cl21 VS lem

Common Lisp editor/IDE with high expansibility
githut

54 935 5.2 JavaScript cl21 VS githut

Github Language Statistics
ulisp

33 361 2.6 C++ cl21 VS ulisp

A version of the Lisp programming language for ATmega-based Arduino boards.
cl-lsp

13 200 0.0 TypeScript cl21 VS cl-lsp

An implementation of the Language Server Protocol for Common Lisp
generic-cl

13 123 0.0 Common Lisp cl21 VS generic-cl

Generic function interface to standard Common Lisp functions
InfluxDB

www.influxdata.com sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
drracket

4 441 7.7 Racket cl21 VS drracket

DrRacket, IDE for Racket
Kawa

3 - - cl21 VS Kawa
rutils

2 245 0.0 Common Lisp cl21 VS rutils

Radical Utilities for Common Lisp

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better cl21 alternative or higher similarity.

Suggest an alternative to cl21

cl21 reviews and mentions

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
11 projects | news.ycombinator.com | 2 Oct 2022

> 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?
2 projects | /r/Common_Lisp | 6 Feb 2022

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).