Eli the Bearded <*@eli.users.panix.com> writes:
This is an older (2018) blog post about a concurrency method the author
has implemented as a Python library. There's nothing inherently Python
about the method, and the title makes reference to the command used in
Go (golang) for creating new threads while also referencing the famous Dijkstra piece. Along the way it has a detour through FLOW-MATIC[*] for anyone who really doesn't understand _what_ Dijkstra was complaining
about in "Goto Considered Harmful".
Notes on structured concurrency, or: Go statement considered harmful
https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/
It's a pretty good read and persuasive about issues with current
concurrency.
Really good read. Thank you. It hasn't been easy to find good reads
like that. I keep on reading good stuff, but usually they are papers
from decades ago.
Very nice summary of the meaning of these various concurrency primitives
out there in so many different languages. Also appreciated the
connection back to the sources --- Dijkstra /et alia/.
Why do I like it? I think it's because the author is concerned with
*clarity*, *generality*, guarantees. Sometimes it seems nobody cares
about these things.
What did I miss? I didn't see any mention to continuations.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)