[nequo]

> I also use Racket, and I think it is a fine language, but for my use cases it doesn't really come close to the experience with Common Lisp.

You mentioned in another comment that you use CL to prototype low-level computations. I assume that this is the use case that you are referring to.

Do you mind sharing why CL works better than Racket for prototyping in this domain?

Or do you have another use case for which Racket is less fit than the one I understand?

[medo-bear]

One thing I can do in Common Lisp which I can't do (almost) anywhere else (but including Racket) is proper REPL-based interactive development. Specifically, I can update state without needing to recompile my program. For my use case this is unmatched for prototyping.

As regards low-level stuff, this is very implementation specific (which is OK for low-level programming). Specifically, SBCL allows me to write much faster code than Racket. Particularly there does not need to be a speed cap or even penalty for using a high level language.