Re:Practices for writing high-performance Go
by chessturk on Monday May 06, 2019 @10:11PM
(#19845792)
My experience has been channels are a really good way to make highly concurrent code readable for people who hate concurrency (ymmv).
They aren't as efficient, but using them as a semaphore (i.e. only signaling) can facilitate fairly-efficient, easier-to-read shared memory. But I'm kind of proving the whole...
> You can very carefully design around it only channels
...part of your post.
You can very carefully design around it using only channels but it quickly starts making more sense to just use a different concurrency abstraction.