News for hackers. Stuff that matters.
Re:What is Clojure good at? by swannodette on Monday October 18, 2010 @09:24AM (#1803367)
But of course, nothing in Java forces you to use state and side effects. It's a culture problem, again; but if you use Java libraries from within Clojure, you are going to run into those same culture problems.

This is a known problem. There is an in development feature called Pods that will allow you to use nasty mutable Java libraries as well write your own nasty Clojure mutable code (perhaps for performance reasons) w/o destroying concurrency guarantees. I'm looking forward to see how it shakes out.

Re:What is Clojure good at? by fogus on Monday October 18, 2010 @10:40AM (#1803634)
> w/o destroying concurrency guarantees

Pods will provide more than that since you can provide concurrency guarantees with locks only. However, Pods should additionally help with:

1. Separation of mutation logic and value policy with the Pod handling the underlying juggling 2. Lock order acquisition guarantees

There is more to it than this, but stay tuned for Rich's upcoming talk at the Clojure Conj. :-)

Re:What is Clojure good at? by swannodette on Monday October 18, 2010 @10:46AM (#1803659)
I meant to write "w/o destroying concurrency guarantees and w/o adding undue complexity". With Pods you don't need explicit locking from what I understand, right?
Re:What is Clojure good at? by fogus on Monday October 18, 2010 @10:54AM (#1803700)
> With Pods you don't need explicit locking from what I understand, right?

That is my understanding yes.

Re:What is Clojure good at? by jrockway on Monday October 18, 2010 @12:33PM (#1804121)
Now I am beginning to understand why people like Clojure so much. Instead of calling them "state threads", whose Google results turn up academic papers from the early 90s, they call them "pods", whose Google results have nothing to do with programming.
Re:What is Clojure good at? by weavejester on Monday October 18, 2010 @05:40PM (#1805278)
Having a short name for commonly used structures aids readability. e.g.

    (ref {})
    (atom [])
Instead of:

    (software-transactional-memory-reference {})
    (atomically-mutable-reference [])
Re:What is Clojure good at? by Raphael_Amiard on Monday October 18, 2010 @12:42PM (#1804160)
I can't really tell if you're being sarcastic or not
Re:What is Clojure good at? by strlen on Monday October 18, 2010 @03:02PM (#1804675)
In one company, where Scala is used, they decided to refer to Monads as "comprehensibles" (due to Scala's "for comprehensions", which can be used like Haskell's do statement) in their standard library and documentation: lets everybody use Monads without the knee-jerk reaction of "isn't it some esoteric category thing that Haskell people have to use to do I/O".
Re:What is Clojure good at? by nickik on Monday October 18, 2010 @03:40PM (#1804846)
There is not really alot of documentation yet so you want find any even if you tree more words.