The article is mostly about the power of a lisp dialect. It's kind of "in the tradition" of lisp to write about it in glowing terms. I myself was inspired to learn a lisp after reading several of these types of essays.
It's just that there's a lot of empirical evidence that these grandiose praise is just praise, but not a lot of shipped software, compared to the 'worse is better' languages such as php, javascript or c.
However, this might be due to the fact that in order to write something in lisp, the author has to be pretty clever, but in order to crap out something in php, you don't need very much cleverness and just need grit/effort. And there are many more people who are not clever, but has grit and effort.
For obvious reasons (syntax) Clojure gets lumped in with the other lisps but Clojure is really intensely practical. It makes a number of choices to that effect. The most of important of which is being a JVM language, so you get access to basically all Java code ever written. The builtin collections are very high quality. It's incredibly stable, so the code you write just keeps working regardless of whatever new features they add in the newest version of the language. There are a lot of high-quality libraries that are "done". The immutable-by-default thing makes writing concurrent code much, much easier. Being on the JVM means you don't have to fuss around with cross-compilation. It's fast enough that you rarely need to mess with optimizing it until you reach real scale. I could go on.
I don't even do much Clojure anymore, but when I did, it was hands down the best thing I ever used for work where the main tasks involved moving lots of data around, filtering it, reducing it, etc. Of course Clojure does tend to attract a lot of clever people, but it also attracts a lot of people looking for the tool with the most leverage to get their work done. There is a lot of Clojure out there, just quietly running the back offices of small/medium sized businesses.