He probably could write an interesting clojure piece - if only he left out the uninformed ranting.
What you can do is compare experiences using a given language. E.g. "Our project using language N went quite well", or "I had a good time in Mexico".
Debating the syntax of for-comprehensions, or the value of the subjunctive, may be fun, but it never really leads anywhere.
Is English or Spanish a better language to communicate in for a specific purpose, just like is Python or Clojure a better language to achieve a certain goal in.
So, without the context of that goal a comparison is meaningless.
But, let's say we create a certain application (let's say an accounting program, or a spreadheet) in both clojure and python, feature-for-feature identical, user interface identical and so on, then a comparison becomes possible.
How long did it take to complete the project ?
How easy is it to change the program to conform to some new specification ?
How fast does it execute ?
And so on. It all boils down to the old benchmark problem, a benchmark in a vacuum is meaningless, you have to test using real applications.
But it is rather pointless to debate languages in isolation ("Spanish verb conjugations must lead to more powerful novels", or somesuch).
The same applies to programming languages, I think.