Why Clojure? I’ll tell you why…
Ertuğrul Çetin

I personally find Clojure’s syntax to be atrocious. The entire language reads like a parenthetical afterthought. Full disclosure: in my 10+ years of doing web development, I’ve only ever come across one Clojure project — and the job at hand was to rewrite it to specifically get away from Clojure.

REPL is a secret weapon of Lisp programmers

I agree that this is a much-loved and useful feature, but it’s also pretty prevalent nowadays in languages like Ruby, Node, etc.

[With ClojureScript] there is no mental context switch when you write React for frontend while writing a Java on the server side.

I have to disagree with your “no mental context switching” statement because, as a developer, I’m almost instantly confused by Clojure: Am I writing vanilla Clojure and need to know it’s ecosystem? Am I secretly writing Java and have to know that? Am I writing JavaScript and secretly have to know that? Producing super optimized JavaScript is great, until you have a JavaScript developer who can’t make heads or tails of Google’s compilation. Plus, at the speed at which the JavaScript landscape operates, I’m not sure how Clojure could possibly take advantage of some of the newer tooling and conveniences. Lastly, how do you write Clojure that produces React — does that really exist?

There are currently around 5/6 people with “Clojure Developer” title in Turkey

To me, this just speaks to Clojure’s high barrier of entry. I realize it’s not the best statistic, but according to the 2018 Stack Overflow survey, Clojure is one of the least wanted and highest paying technologies (i.e., you have to pay a lot of money with the hopes of just finding a developer). Furthermore, Clojure didn’t even make the list of most popular technologies.