Why Clojure?
The response to &quot;but is it slow&quot; is pretty disappointingly bad.<p>&gt; No. Clojure is not slow. Oh, look, it’s not C. It’s not assembler. If nanoseconds are your concern than you probably don’t want Clojure in your innermost loops. You also probably don’t want Java, or C#. But 99.9% of the software we write nowadays has no need of nanosecond performance. I’ve built a real time, GUI based, animated space war game using Clojure. I could keep the frame rates up in the high 20s even with hundreds of objects on the screen. Clojure is not slow.<p>If you&#x27;re going to respond to this question at least provide <i>some</i> comparison maybe.<p>But otherwise that anecdote of &quot;I could keep the frame rates up in the high 20s even with hundreds of objects on the screen.&quot; absolutely screams <i>extremely slow</i>. High 20s FPS with hundreds of objects is incredibly bad on the surface of things. Maybe it&#x27;s closures fault, maybe it isn&#x27;t and is instead the fault of whatever was doing the drawing. But it&#x27;s not a good look either way if that&#x27;s the only data point that can be provided.<p>Similarly the IDE&#x2F;dynamic type question seems to have missed the main downside of dynamic languages - lack of good IDE &amp; other tooling support. How well are things auto-completed for me? How well does the IDE warn I&#x27;ve made a type error <i>before</i> I&#x27;ve gone through a long compile &amp; test iteration loop? How well do linters or other things work, or is there some aspect of LISP that means this is just not an issue like it is in other languages?