Tasty » Adam Sampson's concurrency bookmarks

Making the move from Scala to Go, and why we're not going back | Movio Blog edit / delete

POP being one reason: "It's not just the fact that channels and goroutines are cheaper in terms of resources [...] They are also easier to reason about when coding."

to concurrency go language-design process-oriented scala ... on 26 February 2017

libdill edit / delete

Lightweight fork-join concurrency in C.

to c concurrency coroutine lightweight-processes parallel ... on 14 October 2016

Lock-free programming for the masses · KC Sivaramakrishnan edit / delete

"We use take l_fork <*> take r_fork to atomically take both of the forks." Reagents in Multicore OCaml -- which are semantically (more or less?) equivalent to the multiway barriers that Neil implemented in CHP.

to concurrency multiway ocaml reagents synchronisation ... on 14 October 2016

Notes on concurrency bugs edit / delete

A couple of studies (now a few years old) looking at what kinds of concurrency bugs show up in real software.

to concurrency correctness debugging software-engineering ... on 28 August 2016

Visualizing Concurrency in Go · divan's blog edit / delete

The Go community reinventing what occam was doing in the 80s, again. I'm still not sure whether this is a positive thing or not.

to concurrency go visualisation ... on 28 February 2016

Nim Programming Language edit / delete

It's like Python but with a "parallel:" construct and a usage checker. Sounds familiar to anyone? :)

to concurrency language-design nim occam python ... on 22 March 2015

Futures aren't ersatz threads edit / delete

Awfully limiting compared to actual message-passing concurrency, though.

to concurrency futures parallelism ... on 13 March 2015

Taming the Asynchronous Beast with CSP Channels in JavaScript edit / delete

A nice example of the ideas of process-oriented programming being reinvented. (Again.)

to concurrency csp javascript programming web ... on 13 March 2015

On Go edit / delete

A critical comparison of Go and... Algol 68. I would also observe that Go failed to learn even from occam, another Algol-derived language that it's much more closely related to. But I wasn't previously aware of some of the cool features that Algol 68 had; this is a good read.

to algol concurrency go language-design retrocomputing ... on 05 March 2015

Axiomatic validation of memory barriers and atomic instructions [LWN.net] edit / delete

More progress on model checking for memory models on modern processors. The tool described here covers ARM, Power and x86 memory models, and does efficient analysis of (smallish) chunks of code.

to arm atomic concurrency herd intel memory memory-model model-checking power static-analysis x86 ... on 28 August 2014