[job] S.F Bay Area: Enjoy using Clojure to do a bit of everyhing?

Yummly, Redwood City, CA I'm looking for folks who genuinly enjoy using Clojure to do a great variety of things like Backend mobile APIs, Web services, Infrastructre/AWS automation, security scanning, and all sorts of other things. It's really a lot of fun. If you're intersted please email

Re: what does future do after fn finish ?

You may find that using the Claypoole library is the easiest way to handle threadpools: https://github.com/TheClimateCorporation/claypoole Alan On Thu, Feb 1, 2018 at 11:16 AM, Justin Smith wrote: > yes, that's the idea exactly > > also, you might want more fine grained

Re: what does future do after fn finish ?

yes, that's the idea exactly also, you might want more fine grained control of how much parallelism occurs (eg. if every thread is writing to the same physical device, you can often get better throughput by not parallelizing at all, or keeping the parallelism quite limited - it's worth

Re: what does future do after fn finish ?

Thanks folks. I see now! It should be a list of agents not list of futures within agent. Also any task sent to a agent is processed within a thread anyway so I do not need to add future... On 1 February 2018 at 02:17, John Newman wrote: > Ah, he's using one agent, I see.

Re: If Clojure is to blame for the majority of the startup time, why doesn't ClojureScript proportionally slow down the JavaScript startup time also?

2018-02-01 3:24 GMT+01:00 scott stackelhouse : > CRIU seems like it could actually help in this case. In particular, > paired with Docker, I can just restart from a known good checkpoint with > editor loaded, repl up and connected, etc. That would be very nice. >