Thanks a lot for your kind words! :)
1. For several years now, I have been contributing to Charlotte Herzeel's elPrep project, which we originally implemented in Common Lisp. See
https://github.com/ExaScience/elprep/ for that project, and if you select for example the version v2.61 tag, you can still see the Common Lisp roots of that project. At some stage, we have encountered some limitations when using Common Lisp. The language itself is great, and I would still consider it my most favorite programming language. However, until a few years ago, it was not possible to get hold of a Common Lisp implementation with a proper concurrent / parallel garbage collector, and some better memory management that works well for parallel programming became really important. The only mature choices at that stage were C++ (using reference counting through its STL), Go, and Java. We have made some detailed performance comparison, and Go turned out to perform the best out of these three languages. You can read more details about this in two papers:
I started to like Go quite a lot, because it gets a lot of concepts really right (proper lambda expressions - still unique with regard to getting /every/ aspect right about it; using work stealing as the basis for parallelism; proper garbage collector; etc., etc.). I have doubts about other aspects (error handling, but there are panics and recover, so that's fine ;), but overall it is a really well-designed language.
I still prefer Lisp syntax, and would especially like to have a proper macro facility in my language, and that's the main motivation for Slick. (I also need a somewhat minimal Lisp dialect for some other ideas I am currently working on, but I cannot share more information about that yet.)
2."Slick" came out of a search for a name that suggests both "Lisp" and "Go." The letters S, L, and I are in "Lisp", and the sounds of "ck" and "g" are somewhat similar. "Slig" might have been more obvious. ;)
Pascal