On: Structured Concurrency in High-Level Languages

[ashleyn]

In my experience, there's an academic world, and a practical world, and never the 'twain shall meet.

The academic world knew without experience that higher-level structured concurrency was the way to go. It took the practical industry decades of unmaintanable pthread messes to learn the same lesson, but they ultimately learned it.

[rumcajz → ashleyn]

Any interesting links to academic research of higher-level structured concurrency?

[noelwelsh → rumcajz]

Here's one interesting paper: http://www.csc.kth.se/~phaller/doc/haller16-scala.pdf

Here's the general algorithm:

1. Find something interesting

2. Chase the references and read them.

3. Chase the citations (use Google Scholar) and read them, if they're relevant.

You'll pretty soon have an understanding of the general approaches and issues.

(If you throw "coroutine concurrency" into Google Scholar you'll very quickly find citations from the 80s discussing this model.)

[joker3 → noelwelsh]

You forgot the step where you beg, borrow and steal to get around the journal paywalls.

[noelwelsh → joker3]

Most researchers in programming languages publish their papers on their home pages. In CS Ed I'm discovering it's very different.

[girvo → joker3]

Sci-hub makes it too easy now!