Earlier quoted context omitted.
Every company likes to hear about increased productivity and less bugs, and that's what Clojure/Script gives you. The trade-off is you get less resumes when hiring. The plot twist is the resumes are much higher quality.
Ha. I personally have sat in a meeting where a clojure enthusiast was explaining how he had quickly built a system. He could not explain the code he had written only three weeks before. Clojure suffers heavily from a “less code is good code, write clever code not verbose code” culture. For newcomers this creates dumpster fires that are quick to create and impossible to maintain. Anywaaay, long story short: no. It doe…
Less code can be good code, but they largely are orthogonal axes. Without good abstractions, it doesn't matter whether code is dense or verbose, it will be bad and difficult to grok.