5 ms·
The great thing about Clojure is that it's not tied to the JVM. JVM is just one of the hosts. So I mostly do frontend development at the time and I know Clojur
by diggan 7y ago
The great thing about Clojure is that it's not tied to the JVM. JVM is just one of the hosts.
So I mostly do frontend development at the time and I know Clojure since before. Because of those two variables, I've chosen to use ClojureScript so now I 99% of my professional time write only ClojureScript, with the remaining time being 1% JS when needed. Otherwise the only time I see JS is when I have to understand how a library works.
So I agree with you on the Java side, I'm not a Java developer and I want to stay far away from it, but I love Clojure and I need to be close to it, any other language feels inefficient and slows me down. But there are other hosts you can use, if needed.
- tzjmetron 7y agoUse Common Lisp for a real practical Lisp.
- diggan 7y agoAnd since there is always someone who jumps in saying "Common Lisp is a true lisp while Clojure is not", read https://en.wikipedia.org/wiki/No_true_Scotsman https://en.wikipedia.org/wiki/No_true_Scotsman so we can have a real discussion about the difference ;)
- kazinator 7y ago"No True Scotsman" is about moving the goalposts regarding to the quality or suitability of something. We wouldn't reasonably say that a Dane isn't a True Scotsman, right? A piece of crap unsuitable for production use could be a Lisp. Lisp 1.5 is Lisp; I wouldn't use it today. Lisp or not is not about quality, but semantics. Clojure lacks or changes numerous semantics which define Lisp. That's not statement about quality, just otherness. Clojure doesn't call itself a Lisp; though the main website claims it is a Lisp dialect. Dialects are defined by mutual intelligibility. An Osaka man speaks a dialect which is understood in Tokyo. The mutual intelligibility between Lisp dialects and Clojure does not extend very far beyond (+ 2 2).