Talking about lisp in 2016 is mostly just debating static vs. latent&#x2F;dynamic typing. The lisp guys were talking up their advantages in the 80s&#x2F;90s era of fortran and C and really bad c++, and I guess the really shitty original JVM. It&#x27;s a discussion from a dead age.<p>latent&#x2F;dynamic typing and also macros work very poorly when the codebase is large and there are many people involved, or when we&#x27;re talking about decade plus code-base lifespans. It&#x27;s that simple. If you&#x27;re one or three noticeably smart dudes building a system from start to ultimate finish (financial exit in four years?), why not go with LISP or something like it. If you&#x27;re a team of one or two I advise you do go with lisp or perl or python or erlang or whatever.<p>But that&#x27;s not the systems anybody builds or maintains much anymore. We make things that a rotating cast of 100 might touch over 30 years. We need static typing.