Re:Is Clojure dying, and what has Ruby got to do with it?
by philbo on Thursday May 25, 2017 @04:39PM
(#14419978)
As a JS programmer with some Clojure experience I can confirm that the JVM is absolutely the biggest turn-off for me personally. Lisp syntax, immutable data structures, laziness, all splendid. The build/runtime environment, not so much.
Sounds like I should revisit CLJS based on your comment.
Re:Is Clojure dying, and what has Ruby got to do with it?
by ledgerdev on Thursday May 25, 2017 @05:14PM
(#14420194)
Well at the moment, the tooling is all lein/JVM based.
That said, Figwheel hooked up with atom+protorepl+parinfer is pretty amazing if you haven't tried it.
Re:Is Clojure dying, and what has Ruby got to do with it?
by lsdafjklsd on Thursday May 25, 2017 @11:28PM
(#14421805)
Parinfer is a huge game changer. Everyone afraid of writing lisp needs to try again using parinfer.
Re:Is Clojure dying, and what has Ruby got to do with it?
by lilactown on Thursday May 25, 2017 @06:10PM
(#14420554)
As a JS developer using CLJS in my spare time, I've found that once I got my project setup with figwheel and everything, I can pretty much ignore the JVM. The moment that "classpath" is mentioned I usually try to find another way, though.
Re:Is Clojure dying, and what has Ruby got to do with it?
by owebmaster on Thursday May 25, 2017 @05:38PM
(#14420318)
I like leiningen. The stability is something I never saw anywhere. You have plugins without updates for like 2 years and working like it was updated recently. Although it is becoming less common for clojure/script projects to be unmaintained.
For the JS developers out there, is this something that's of interest? Or is the existing tooling(lein) good enough? What would be your ideal tooling story?