> Plus it compiles to a jar, so anywhere a jar will run - so will clojure. I'd add, for those who don't know Clojure, that as /u/jwr commented in this thread:

> Plus it compiles to a jar, so anywhere a jar will run - so will clojure. I'd add, for those who don't know Clojure, that as /u/jwr commented in this thread: Clojure also runs anywhere there's a browser, thanks to ClojureScript. And thanks to source file that can be shared between both Clojure and ClojureScript (.cljc source files), you can have the very same Clojure code and run it both on the front-end and on the back-end. So not only the JVM "reaches" (as Rich Hickey says), but JavaScript reaches too. > ... only accessible to dragons who can write emacs plugins blindfolded and upside down I know you're joking but although I use Emacs since forever and can configure it to my liking and can eventually come up with some elisp code doing what I need, I'm not good at elisp by any means. But I'll admit that learning both Emacs + elisp + Clojure at the same time for someone who's never learned any Lisp dialect is going to be hard (and a very hard sell). Now there's a Clojure LSP server (which should help) and it works not only from Emacs but also from other IDEs. It's not mandatory to use Emacs for Clojure development even if many (most?) Clojure devs do use Emacs.