If you&#x27;re asking yourself what kinds of problems is a Lisp good for you should probably watch this: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=8X69_42Mj-g" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=8X69_42Mj-g</a> (A computational chemist built himself his own Common Lisp implementation because no other language available was powerful enough for his needs...)<p>It basically boils to: if you&#x27;re solving a <i>truly new and interesting problems</i> for which the current libraries and ecosystems don&#x27;t matter that much to you anyhow (because what you do is too bleeding-edge &#x2F; ahead of everyone else, so you&#x27;ll write your own better stuff anyhow), than you might want to choose a Lisp.<p>And if your problem is so bleeding-edge and exotic that you also need to build your own programming-language for it, than you might just as well build yourself a Lisp (like the guy in the video did) and add your needed features to it, because this would be easier than any other approaches and allow you to spend more time on your problem and not on the language...<p>EDIT+: another example is DWave using SBCL: <a href="http:&#x2F;&#x2F;www.dwavesys.com&#x2F;careers&#x2F;senior-software-developer" rel="nofollow">http:&#x2F;&#x2F;www.dwavesys.com&#x2F;careers&#x2F;senior-software-developer</a> - if quantum (or analog... anyway...) computing is not &quot;truly new and cutting edge&quot;, than I don&#x27;t know what is