In other words, I never coded something sufficiently big to understand the pros of CL.
Hence, I'm curious. What stuff I'm missing out in terms of language features and libraries?
use common lisp (sbcl) if you want c-level performance
use common lisp if you want to make optimizing compilers
use common lisp if you want smalltalk type repl driven interactive development
The new Racket compiler was derived from the Chez Scheme compiler.
On r/lisp there was a rant that included a reflection that things would be done in a third the time. There was an ask for $60M to apply Lisp to know a different world. Apple can easily afford a $180M experiment to see Ralph/Dylan implementation of iOS/macOS. If proved successful would the software platform leap how the hardware has done across multiple architectures? The ARM M series devices are a there and back again move given Apple Newton was on ARM and Apple invested which kept the idea alive.
https://download.clojure.org/papers/clojure-hopl-iv-final.pd...
The design decisions in this paper strongly resonate with me. It helped me to overcome my aversion to JVM-hosted languages, and settle down to learn Clojure.
I'm a research mathematician, at one extreme where code is steps up a mountain. I don't need to summit twice, so productivity is far more important than speed. Nevertheless, the fastest Clojure time trials use GraalVM:
AFAIK, the only (more known) uses of Racket is as a scripting language for Naughty Dogs PS3-era games, and it was made to make Arc (which runs HN).