I was thinking of the functions as described by the Common Lisp HyperSpec. Reading it makes me cry.
It is not unreasonable to call that a 'standard library.' The term 'standard library' is often used to describe built-ins.
The age of the CL core functions is a genuine weakness, specifically in terms of performance. No matter how many libraries you download from Quicklisp, they still have to be implemented in something, and if that something is antiquated or clunky, you're essentially asking the compiler to optimize the entire language out of existence to keep up with the state of the art. The same applies to npm, pip, cargo, and all the rest.
It is not unreasonable to call that a 'standard library.' The term 'standard library' is often used to describe built-ins.
The age of the CL core functions is a genuine weakness, specifically in terms of performance. No matter how many libraries you download from Quicklisp, they still have to be implemented in something, and if that something is antiquated or clunky, you're essentially asking the compiler to optimize the entire language out of existence to keep up with the state of the art. The same applies to npm, pip, cargo, and all the rest.