For most people clojure/clojurescript is the way to go as it's practical for building modern software. I'm working on something (but very slowly as I have a dayjob) to do this. I wish we had started in clojure(script), but that was not my call at the time (it is now).

But in short; for now clojure(script) is the most practical way currently.

Note: there is ABCL for running CL on the JVM, so for that you don't need clojure (I haven't tried but I have friends who use it and say it works well), however the JS issue (and I would need JS and interact with JS) isn't solved yet, as far as I know. I haven't looked recently, but threads like [0] are not that old and I cannot quickly see many things changed in that respect. So I would rather opt for what CLOG did and other Liveview type of systems, so it doesn't matter what happens in the frontend. WASM and (because now it's still needed) a robust JS implementation would be great.

[0] https://news.ycombinator.com/item?id=21535165

ECL runs on wasm via Emscripten.

Sorry, off topic, but recently I tried using ECL as my daily driver after I setup Emacs and Slime to use it. It was fine for dev as well as deployment. I did go back to using SBCL and LispWorks after this experiment was over.

There is a rich ecosystem of CL implementations. I don’t use it much at all, but ABCL is really interesting also if you work on the JVM.

While Clojure is a great language, I would say it does not offer the same REPL driven experience as Common Lisp because it runs on the JVM.

Common Lisp (SBCL) and CLOG is worth checking out first.

The magic I described in the original comment exists in Clojure but you can feel its true power in Common Lisp.

It helps when one shells out a license for Cursive, https://cursive-ide.com/

Agreed, but people usually want practical first.