Basically almost every Lisp out there has a major downside that turns me off from using it to the extent I consider using Haskell’s s-expression tolerance (like (map odd [1,2,3]) (((.) fst snd) (1,(2,3)))) (which, obviously, would be a very bad practice): 1. Common Lisp: Classical OOP everywhere, very bad build automation and packaging (asdf), available implementations have low support availability, bugs are everywhere due to the limited teams who are working on those. 2. Scheme: Same as CL, in addition to the scarce language support in most editors (not sure even if it has LSP support), also it’s hard to find libraries/packages to build something on. 3. EuLisp, ZetaLisp, MacLisp, InterLisp, ISLisp, T, Arc, PicoLisp: I still find it hard to believe those are not in the museum of computing yet. 4. Guile, Racket: both look so promising but the lack of interest from community which results in an effect on the number of available packages to build on, makes it much harder to start a new project in any of them without reinventing the wheel. 5. Clojure: aside from the JVM dependency and the build system hassle, the language is just too big, still the most plausible option in this whole list though.

I’d always prefer a Lisp. But ideally, Go wins (more at The Prefect Programming Language) by its unauthoritarian package manager and not using exception handling. As aforementioned @ A thought about Clojure, I think Clojure is the modern day Lisp that works very good for interactive programming and rapid development. But here’s another killer feature of Go that roughly does not exist elsewhere: the great STD. With Go, I can feel very comfortable writing a Go application without the need of checking the internet for questions or 3rd-party libraries, eventually I might need to, but if compared to any other tool I’ve ever used, it’s amazing (back in the day when I used C# I’d need a web browser always running alongside to my IDE). I do not have internet connection those days and while playing tracks I thought of building a simple CLI to handle my audio tracks synchronization, I know how to do it without reinventing the wheel in Go, with only using the STD, with Clojure, it’s going to be unrapid developement.

Found out that Clojure has Go-like channels. https://clojure.org/guides/async_walkthrough, very promising to use it (as mentioned at a thought about Clojure)

I wrote on The Prefect Programming Language my thoughts about what would be the prefect language out there, and what would be the nearest thing of it. It’s C and this is not going to change (any far at least), however, perfect is not always practical. I still believe in Lisp-like syntax superiority and I love the flexibility of dynamic typing and dynamic loading, and C has both already. Still C lacks many things like a proper build system (that convince everybody) and packaging.

From the list on that article, I’d be left with Julia and Go, Julia has two downsides of the Centralized Package Repository and the use of Exception handling. And Go has the downside of not having a REPL. For me, when it comes to the real world, the issue with centralization does not matter more than the issue of getting the work done (i.e. REPL weights more).

Going more practically from there, I see a high potential with Clojure, it does not have the OOP trash like Common Lisp and it is a Lisp, it is not too new like Jack, and it can interlope with Java. Perhaps it’s the go-to language for me right now. Displacing Common Lisp.