I now generate ALL of my hobby projects in CL (SBCL on windows). I tell the LLM to 'over-comment' the code, so I get to learn as I read the output. It has been glorious. I generally use the web browser on an unused port on localhost for user IO (beautiful pages), and the app just hooks to Hunchentoot to serve.
Any 'real' programming language (meaning, one that is truly general purpose: numeric stacks, Web front and back ends, system code, utilities, etc) will always have some cruft. In CL, at least you can understand why some cruft exists. And you get used to it, because it's not like e.g. C where there are some very dark corners indeed. Check out Peter's book!
CL lets you build real apps, for real. No toys. This has value.
As opposed to other languages where you don't build real apps? I don't think anyone was arguing you can't make real apps in CL
My push into Common Lisp was a current revision of a classic AI textbook that mixed up usage of nearly the complete history of lisp because some of the examples presumably dated to the 1960s/1970s with moderate adjustments to make sure that they still compiled in SBCL or the like, so it was a natural lesson from that textbook. Maybe not the best way to learn Common Lisp, but that was an interesting semester for me. (I and the few other people in the class that semester decided to learn Lisp by choice for the class and I think I was the only one to also decide "I'll do every assignment with implementation language choice in Common Lisp this semester", which was most of my classes, just to keep grad school interesting.)