The Perils of Clojure

Ready to unravel the mystery? Despite the skeptical title my faith in Clojure is unshakable. I think functional languages are to save the software world and the power of LISP-like languages — read homoiconic, macros & stuff — is just too hard to be ignored. And the intersection of those two powerful concepts plus the incredibly simple data model and a bunch of other nice things (like running on top of JVM) is Clojure. Quite frankly I don’t think there’s any other language out there that’s better suited for general purpose programming. <img alt="" src="https://miro.medium.com/v2/resize:fit:770/1*2Q5CCk7sK9MTZWlCALVObQ.jpeg" style="height:700px; width:700px" /> That’s now a classic… Being a huge fan though, I must admit that some time ago after reading <a href="http://winestockwebdesign.com/Essays/Lisp_Curse.html" rel="noopener ugc nofollow" target="_blank">The Lisp Curse</a> I realized the same curse is cast over my favorite language too — but admittedly in a much milder form. The Lisp curse? In a nutshell too much power means less or no hardship; no hardship — no community. I mean does someone like Thanos need a community? Nope, he snaps his fingers — done. And to counter that you need the Avengers + a bunch of other superheroes, ingenious ideas, bold thinking, special effects, millions of dollars to make a bunch more movies, etc. Basically, a community defined by hardship… Sans the millions, I guess. <a href="https://medium.com/@ignorabilis/the-perils-of-clojure-1ec555de9ef9">Website</a>