> Because the only thing Go did was bake CSP into the language, it is nice, but not a solution for every concurrency problem.
I'm not sure I understand your sentence. Are you saying that communicating sequential process only works because it is first class in Go or that CSP is not a solution to every concurrency problem ?
It is not a solution to every concurrency problem.
I tend to use languages that give library writers (almost) the same control as the language itself has.
EDIT: To expand a little more into what I mean. In most languages that offer async/await, that is mostly syntactic sugar (with some compiler help) to the blessed task pool library.
A good way to explore that is to see the parallel libraries available in C++, JVM, .NET, Haskell and OCaml worlds.
I'm not sure I understand your sentence. Are you saying that communicating sequential process only works because it is first class in Go or that CSP is not a solution to every concurrency problem ?