News for hackers. Stuff that matters.
Re:Introducing Drake, a kind of ‘make for data’ by abraininavat on Thursday January 24, 2013 @01:15PM (#5111090)
Why Clojure?
Re:Introducing Drake, a kind of ‘make for data’ by hvs on Thursday January 24, 2013 @01:30PM (#5111198)
Probably because that's one of the languages that they use internally.

http://www.factual.com/jobs/oTR1Vfwq/Software-Engineer---Pal...

Another answer would be, "Why not?"

Re:Introducing Drake, a kind of ‘make for data’ by aboytsov on Thursday January 24, 2013 @02:45PM (#5111715)
We love Clojure. Lisp is an extremely powerful language, and Clojure brings all this to the practical JVM world. And Lisp is quite good in operating on lists and graphs, which is a big part of Drake.
Re:Introducing Drake, a kind of ‘make for data’ by pencilcode on Thursday January 24, 2013 @06:53PM (#5113060)
out of curiosity, why did you go the clojure route instead of the scala route? From what i understand, scala has more libraries available, including ai and nlp libraries but maybe my impression is not correct?
Re:Introducing Drake, a kind of ‘make for data’ by aboytsov on Thursday January 24, 2013 @07:17PM (#5113161)
It's hard to compare Clojure and Scala. Scala is a multi-paradigm programming language with strong OOP support and functional support. It's arguably more verbose than Clojure but looks much more similar to Java.

Clojure is a Lisp. Lisp stands aside all other programming languages, first of all, because it supports syntactic abstraction (a.k.a. "code is data"). Hardcode addicts (I'm not one of them) say there are only two programming languages - Lisp and non-Lisp.

Here's a good comparison of Scala and Clojure: http://stackoverflow.com/questions/1314732/scala-vs-groovy-v...

When we made the decision to switch to Clojure, several things affected it, in no particular order: - we had some people who were already very proficient in Lisp - we liked how expressive and compact it was - Lisp is considered to possess immense expressive power (see http://www.paulgraham.com/lisp.html) - we were enamoured by Cascalog (http://nathanmarz.com/blog/introducing-cascalog-a-clojure-ba...), and it's written in and for Clojure. This one payed off very well. - Lisp has a reputation of being great at manipulating data: lists, graphs, etc.

Here's a good answer from one of our engineers: http://www.quora.com/Clojure/Why-would-someone-learn-Clojure

As for libraries, both Clojure and Scala are JVM-based, and Clojure has a very good syntax for Java interop, so all Java libraries are available to us. But, of course, Clojure community also spits out libraries like crazy, for example, take a look at this marvel which we use in Drake for parsing: https://github.com/joshua-choi/fnparse.

Re:Introducing Drake, a kind of ‘make for data’ by pencilcode on Friday January 25, 2013 @07:17AM (#5115080)
Thanks for your feedback. I've been playing around with both languages, and was leaning towards scala since it seemed more likely i could use it professionally, even though i liked clojure a bit more, sortta like the lisp like syntax.
Re:Introducing Drake, a kind of ‘make for data’ by dirtyvagabond on Thursday January 24, 2013 @07:59PM (#5113311)
another way to look at this is: we didn't say to ourselves, "we have to be on the JVM, so which JVM language should we use"?

instead we asked, "what would be a great language for this project?" and arrived at Clojure based on the above.

Re:Introducing Drake, a kind of ‘make for data’ by SilasX on Thursday January 24, 2013 @06:53PM (#5113059)
Some see a Lisp and ask "why"? I see a non-Lisp that could be replaced with a Lisp and ask "why not?"