Why we picked Clojure

#1

Post by dale-cooper » Tue, Dec 01, 2015, 9:43 AM UTC

Re: Why we picked Clojure

#2

Post by dozzie » Tue, Dec 01, 2015, 10:27 AM UTC

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

#3

Post by bitlax » Tue, Dec 01, 2015, 11:38 AM UTC

dozzie wrote: post #2

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 b…

"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

#4

Post by dozzie » Tue, Dec 01, 2015, 1:12 PM UTC

bitlax wrote: post #3

dozzie wrote: post #2

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 b…

"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.

> Then don't use it, right?

I don't. Though I would like to from time to time.

Re: Why we picked Clojure

#5

Post by GigaMos » Wed, Dec 02, 2015, 2:35 PM UTC

dozzie wrote: post #4

bitlax wrote: post #3

Earlier quoted context omitted.

"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.

> Then don't use it, right? I don't. Though I would like to from time to time.

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.

http://blog.fikesfarm.com/posts/2015-08-22-planck-works.html