>Bad clojure code is unmaintainable spaghetti code; which gets worse over time, as people attempt to 'patch on' fixes without doing the heavy lifting of trying to figure out:
Couldn't you say the same thing about most languages?
That would be my take on this too. If you get code written by people who don't know the language, the result is pretty much always dreadful. I know of no language that mitigates this.
However, I'd be interested in which parts of Racket and CL klibertp thinks are making them better languages than clojure.
Couldn't you say the same thing about most languages?