On Tue, Aug 23, 2016 at 10:59 AM Sergei Koledov <grey3...@gmail.com> wrote:
> Thank you! I know about Java's thread pools, but I want to do my job in > clojure-idiomatic way and possibly less using java interop. > > I think many of the use-cases for refs/agents are supplanted by core.async. In this case, the 'pipeline' family of functions can be used much like an executor pool. I'm not sure how idiomatic STM can be, when I've rarely used it. I think in most cases where you'd want to coordinate multiple refs within a transaction, a single atom is going to be much simpler and performant enough. I think clojure uses the 'toolkit' approach, in that it allows many things to be combined and encourages composition, but it doesn't prescribe or force you towards any particular shape of solution. That's a natural consequence of 'design by decoupling'. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
