A Case for Clojure and GraphQL: Replacing Django
Outside of very special circumstances, I don&#x27;t think it is a good idea to replace Python code with Clojure code. In fact, judging from my own contracting experience and seeing the many mistakes made by first-time Clojure programmers, I more often than not suggest moving from Clojure to anything else.<p>The problem with using esoteric languages is multi-fold. First, you have to trust that the original programmers actually know the language enough to not create a massive disaster. Are they comfortable working without a framework, are they knowledgeable about all the issues that arise from building closer to the metal, so to speak? It seems to me that the answer is &quot;no&quot; more often than &quot;yes.&quot;<p>Once this happens, you end up in a read-only code situation, and this is a problem because they leave the project with tons of bugs and downright stupid decisions. You are then left in the position to ask 15 people if they can make dollars or sense of anything written, and if you are fortunate, you will get one &quot;yes.&quot; I joke that I know all 50 Clojure programmers in the US, and sadly, that&#x27;s not much of an overstatement. If you want your code to exist, and you aren&#x27;t a real somebody, then good luck. If you aren&#x27;t located in SF, LA, or some other city that attracts talent, definitely do not use Clojure or any other esoteric language!<p>Of course, I didn&#x27;t read the article, as it isn&#x27;t loading at all.