Comment on What is Clojure good at?parentComments−fogus15y> w/o destroying concurrency guaranteesPods 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 guaranteesThere is more to it than this, but stay tuned for Rich's upcoming talk at the Clojure Conj. :-)−swannodette15yI 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?−fogus15y> With Pods you don't need explicit locking from what I understand, right?That is my understanding yes.
Comments
> 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. :-)
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?
> With Pods you don't need explicit locking from what I understand, right?
That is my understanding yes.