Re:Why we picked Clojure
by dozzie on Tuesday December 01, 2015 @05:27AM
(#10654495)
Clojure would be a nice environment to work with if it wasn't running on JVM.
It renders Clojure a resource hog, and the startup time is awful. A big no-no
for most of my use cases.
> Python’s mysql and postgres database drivers required compilation. This made both developer machine setup as well as deployment more complicated than it really needed to be.
Not quite. You made setup more complicated than it needed to be. Ever heard
of binary packages?
Re:Why we picked Clojure
by bitlax on Tuesday December 01, 2015 @06:38AM
(#10654653)
"Clojure would be a nice environment to work with if it wasn't running on JVM. It renders Clojure a resource hog, and the startup time is awful. A big no-no for most of my use cases."
Then don't use it, right? There are plenty of use cases for which Clojure makes sense, and where running on the JVM is a perk.
Re:Why we picked Clojure
by GigaMos on Wednesday December 02, 2015 @09:35AM
(#10663120)
ClojureScript is these days selfhosting. If you want to write and run small scripts you could give Planck a try (ClojureScript REPL). The startup time is much smaller.
> Python’s mysql and postgres database drivers required compilation. This made both developer machine setup as well as deployment more complicated than it really needed to be.
Not quite. You made setup more complicated than it needed to be. Ever heard of binary packages?
Then don't use it, right? There are plenty of use cases for which Clojure makes sense, and where running on the JVM is a perk.
I don't. Though I would like to from time to time.
http://blog.fikesfarm.com/posts/2015-08-22-planck-works.html