Re: [ANN] components.md

> > >> > The thing that this doc also advocates (and I am against) is manual >> dependency management, your app start function must call start on its >> dependencies. This not only hardcodes the dependency, but also requires the >> user to think about the startup order of components on every usage.

Re: Advice getting started with concurrency and parallelism in Clojure

On Tuesday, April 5, 2016 at 6:51:59 PM UTC-7, tbc++ wrote: > > If it all seems confusing, do not despair, there's two things that will > handle the vast majority of the use cases you may have: > > 1) `future` - spawns a thread that runs the body of the future ( > https://clojuredocs.org/clojur

Re: Advice getting started with concurrency and parallelism in Clojure

The biggest problem with pmap I have is ordering, ie. it will process in batches of (+ 2 (.. Runtime getRuntime availableProcessors)), and only take a new batch when the slowest of the old batch has been evaluated. With functions dependent on IO, parallel gains are only a fraction of what they

Re: [ANN] components.md

> On 7 Apr 2016, at 13:42, Jeroen van Dijk wrote: > > > > The thing that this doc also advocates (and I am against) is manual > > dependency management, your app start function must call start on its > > dependencies. This not only hardcodes the dependency, but also requires the > > user to

Re: Advice getting started with concurrency and parallelism in Clojure

The two resources that helped me most with concurrency and parallelism are "Java Concurrency in Practice" and "ZeroMQ — The Guide". Introductory Go books are also enlightening. Once you have a clear understanding of the underlying concepts in general, understanding how they are accessible in Cloju

Re: Advice getting started with concurrency and parallelism in Clojure

Exactly. Clojure's strength is constraining mutability. How each primitive constrains mutability is different. Note: that many of these defaults can be overridden if the user really knows what they are doing. atoms - given a mutable cell, provide a function to update the data, may be run multiple

Re: Advice getting started with concurrency and parallelism in Clojure

Niels-- Ah, interesting. My uses of pmap haven't been I/O bound. I didn't know about the claypoole library. Will keep that in mind. On Thursday, April 7, 2016 at 8:00:39 AM UTC-5, Niels van Klaveren wrote: > > The biggest problem with pmap I have is ordering, ie. it will process in > batches

Re: [ANN] components.md

Ah, discussions which do not define terms are subject to endless round and rounds. I see several characteristics of a component. The first is that there is a lifecycle. A component may need to be opened and closed. The second is that components are not singletons. So you can have multiple inst

[ANN] Nightcode 1.2.0 with "smart" indentation snapping

Nightcode's recent Parinfer integration is finally starting to stabilize. This latest release adds an (allegedly) smart indentation snapping feature. Instead of tab and shift+tab always moving your code two spaces, it moves it to the next semantically me

Re: Upgrading to Clojure 1.8 (direct linking)

On 4/6/16, 1:21 PM, "Piyush Katariya" wrote: > Has anybody experienced the performance boost by switching to Clojure version > 1.8 (and direct linking) ? We switched to direct linking in stages. We first moved from 1.7 to 1.8 (which brought a direct-linked core). Then we enabled direct-linking

Re: Upgrading to Clojure 1.8 (direct linking)

On Friday, April 8, 2016 at 5:50:33 AM UTC+9:30, Sean Corfield wrote: > > On 4/6/16, 1:21 PM, "Piyush Katariya" on behalf of corporat...@gmail.com > wrote: > > Has anybody experienced the performance boost by switching to Clojure > version 1.8 (and direct linking) ? > > We switched to direct l

Re: [ANN] Aleph 0.4.1

This is considerably simpler than the suggestions in this thread, but I've written a very basic statsd client and server in the literate examples: http://aleph.io/aleph/literate.html#aleph.examples.udp. Feedback is welcome. On Saturday, April 2, 2016 at 11:44:53 PM UTC-7, Zach Tellman wrote: >