Troll: a person who makes a deliberately offensive or provocative online post.
You don't have to be wrong to be a troll, you just have to unhelpful and provocative. Which is what your comment was. You just said "its useless" without even providing the smallest effort in terms of an argument.
Two wrongs don't make a right. If you thought that OP was making bad arguments then make good ones.
Personally, i know 4 languages rather well and i do write everything in clojure first and then translate it.
OP's article is called "Why i'm more productive in clojure" This sets a tone that doesn't require evidence because its a very personal. If readers choose to interoperate that as "clojure is better" then i can't blame them, but the author at least had the decor to not state their opinions as evidence.
In terms of evidence for anything Programming language related, even if you had read every study, your still going to consider your projects needs. So even if Clojure showed a reduction in bugs over java (https://news.ycombinator.com/item?id=8558740) you should still consider other factors.
So many libraries in Clojure that lead to serious productivity benefits rely on macros, which in turn are possible because of homoiconicity. It's more than useful, it's a key ingredient in the power of the language. You can extend and embed the language or sub-languages or quickly write a particularly potent DSL in just a few lines of code in Clojure thanks to this feature.
Compare this to language that offer macros but without homoiconicity and the benefits are clear. The two different ways to write macros in C and C++ involve language semantics and syntax that are quite different from the regular syntax. In Clojure, the language is identical, you can actually control the compilation process using the same regular Clojure code that you use everywhere else. It's really quite amazing how far this gets you.
I also think macros are what keeps the language clean long term. Since most things can be expressed in user space using libraries, you don't have to bolt them onto the core language.
As time goes on, usage patterns change and something that might've seemed like a good idea at one time can become an anti-pattern later. Clojure has stayed remarkably small and focused over the years while the way it's used has changed significantly.
