The author is right. This was a great read. The LISP family has some of the highest potential of any language. Amazing things were done with it, from software to hardware, in the 70&#x27;s and 80&#x27;s. Then, after politics and Common LISP, it&#x27;s been pretty stagnant while most of the best stuff happens outside it in about every attribute. Often, someone ports such works right back to Common LISP to show it could do it all along. It just didn&#x27;t due to a combo of language and community issues it will never fix.<p>Leads to two conclusions. The first is for the author to open-source, if it hasn&#x27;t been, these analyses and work in the article so people can start fixing up a version of Common LISP. The second is to ignore Common LISP entirely in favor of a newer project like Racket Scheme that builds on better, more-consistent foundations with good community and batteries included. It&#x27;s become most of what I expected of the Common LISP&#x27;s while Common LISP withered.<p>The third result is some brave academics need to implement a Genera clone using Racket or Chicken. The rapid iteration, live updates, and whole-system debugging should be preserved. Also feature a deploy-to-executable model that can run in more suitable environments (eg desktops, containers). That would be badass.