Why use Clojure?

Re:Why use Clojure? by wonderzombie on Tuesday December 24, 2013 @01:31PM (#6960507)

You don't need to "know Lisp" in the sense of being proficient, but you need to be familiar with s-expressions. Once you grok s-expressions, the rest is "just" grokking a bunch of functional idioms not specific to Clojure.

Actually if you're familiar with Haskell then Clojure idioms should be more familiar to you. Clojure's datatypes are (almost all) immutable, driving it towards a lot of functional idioms you see in such as Haskell or maybe Scala.

[ Parent | on HN ]

Re:Why use Clojure? by catnaroek on Tuesday December 24, 2013 @09:00PM (#6961913)

Immutability is not the whole story. There is also parametric polymorphism, algebraic data types and pattern matching (best case analysis tool ever), type classes for type constructors (not just types), etc.

[ Parent | on HN ]

Re:Why use Clojure? by wonderzombie on Wednesday December 25, 2013 @06:44PM (#6964724)

Of course. That said, Clojure doesn't have those, given that it has a dynamic type system and destructuring instead of pattern matching (not as clean, IMHO), so a comparison to Haskell in this respect is less useful.

[ Parent | on HN ]

Re:Why use Clojure? by catnaroek on Thursday December 26, 2013 @02:20PM (#6967549)

My point was that it is perfectly possible to be familiar with Haskell and find Clojure (and Lisps in general) puzzling.

On the other hand, I would be genuinely surprised if someone familiar with Haskell were unable to pick up ML, or vice versa.

[ Parent | on HN ]

Re:Why use Clojure? by dkersten on Thursday December 26, 2013 @06:56PM (#6968719)

If you want pattern matching, check out core.match

[ Parent | on HN ]

Re:Why use Clojure? by catnaroek on Friday December 27, 2013 @01:11AM (#6969590)

Where is the exhaustiveness checking?

[ Parent | on HN ]