Title: I have gone through initial chapters of &quot;Practical Common Lisp&quot;[1] and &quot;Loving Common Lisp&quot; [2], and have a bit of intuition on lisp, and the power of macros. Haven&#x27;t done any projects yet, but was also researching on real issues faced by adopting lisp, and ran into articles about abandoning lisp [3], adopting lisp [4],[5]. Could not find anything more recent; but what they mention in these articles - even the ones that are adopting lisp talk about issues like:<p>* poor ecosystem of libraries - few gems, most other half-baked<p>* poor community coordination<p>* Dependency management limitations with quicklisp<p>And some specific red flags like:<p>* poor support for json[6]
* poor support for async<p>* have to restart the server every 20 days because of some memory leak [3]<p>* hack to tune GC [5]<p>If you are using lisp in production for non-trivial cases, 
do these issues still exist? is there a way you can quantify effort is resolving them, and if yes, what is it?
and, finally, if you had to re-do your project, would you chose lisp or something else?<p>[1]: <a href="http:&#x2F;&#x2F;www.gigamonkeys.com&#x2F;book&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.gigamonkeys.com&#x2F;book&#x2F;</a><p>[2]: <a href="https:&#x2F;&#x2F;leanpub.com&#x2F;lovinglisp&#x2F;read#quicklisp" rel="nofollow">https:&#x2F;&#x2F;leanpub.com&#x2F;lovinglisp&#x2F;read#quicklisp</a><p>[3]: <a href="https:&#x2F;&#x2F;lisp-journey.gitlab.io&#x2F;blog&#x2F;why-turtl-switched-from-lisp-to-js&#x2F;" rel="nofollow">https:&#x2F;&#x2F;lisp-journey.gitlab.io&#x2F;blog&#x2F;why-turtl-switched-from-...</a><p>[4]: <a href="https:&#x2F;&#x2F;lisp-journey.gitlab.io&#x2F;blog&#x2F;why-deftask-chose-common-lisp&#x2F;" rel="nofollow">https:&#x2F;&#x2F;lisp-journey.gitlab.io&#x2F;blog&#x2F;why-deftask-chose-common...</a><p>[5]: <a href="https:&#x2F;&#x2F;www.grammarly.com&#x2F;blog&#x2F;engineering&#x2F;running-lisp-in-production&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.grammarly.com&#x2F;blog&#x2F;engineering&#x2F;running-lisp-in-p...</a><p>[6]: <a href="https:&#x2F;&#x2F;stevelosh.com&#x2F;blog&#x2F;2018&#x2F;08&#x2F;a-road-to-common-lisp&#x2F;#s48-st-json" rel="nofollow">https:&#x2F;&#x2F;stevelosh.com&#x2F;blog&#x2F;2018&#x2F;08&#x2F;a-road-to-common-lisp&#x2F;#s4...</a>
Upvote: