My view is premised upon the idea that a major deficit of Common Lisp is a poor access to contemporary independent user interfaces. The solutions that exist are not competitive with the leverage Clojure enjoys from JVM (and .NET).
Do you think clojure has the potential to be useful in 20 years if the JVM dies today hypothetically? I don't know, I think yes, because it has a bunch of good ideas, but it isn't at all clear. Take JS as an opposite example, if the web is to disappear, JS will disappear as well, no matter how many other platforms it is ported to, it just isn't good enough to stand on its own.
I could be talking out of my ass here, but my point was that CL has a good track record for survival, so it has the potential for a 100 year language, while clojure is yet to prove itself for such a task. These things are extremely hard to predict, tech history has a habit of throwing such wild-cards as personal computing and the web. We'll see.
Today with free SBCL and Clozure (among many others), deployment is free - what I would have given in the 1980s for something like SBCL!
In the 80s SBCL was called CMUCL. Free.
Is there any real connection here with CL? Did these events somehow precipitate or deepen the AI winter?
Clojure really does hit the sweet spot combining a concise agile language with good practical decisions, similar I think to some of the decisions that went into the design of Scala (like a generalized seq API for lots of data structures).
Except for some personal serious side projects, I am now retired, and I chose Clojure over other good possibilities (e.g., Common Lisp, Racket, Gambit-C, Scala, Smalltalk, or Ruby) because it is a practical language and still lots fun to code in.
Now that I don't have to worry about staying up to speed on all of the languages my customers used to like using, I find that just using a single language really saves me a lot of time. Some advice for people still working: perhaps choosing a single practical and extensible language like Scala or Clojure is a good strategy; I used to like being a polyglot programmer but that requires a lot of overhead!
If we're taking the worse-is-better angle My suspicion is that clojurescript, which compiles to javascript, is a much more likely candidate to continue based on worse-is-better.
Hygienic macros often prevent one from shooting oneself into the foot, but they prevent also some truly elegant code. Having lists and vectors with a common interface is cool, but that the semantics of conj is different for both is annoying. Easy java interop is worth a lot, but it prevents call/cc.
It's probable that i will gladly use Clojure for the next 10, maybe even 20 years, but it won't be the programming language my grandchildren will ask me to shut up about.
So we're really talking about dialects of Clojure (and perhaps might as well be talking about dialects of Lisp in general).
Of course I am adopting PG's premise that the 100 year language is a LISP while ignoring his premise that it is not a bit kludged up by practical considerations (i.e. the ugliness of its dependence on the JVM).
(/edit) Clojure also has an evangelist in Rich Hickey whom people seem to respect independently of Clojure.