(whoops, excuse the bad webserver config... should be fixed now) > Don't require users of your API to start goroutines to use your API correctly. Actually, wh

(whoops, excuse the bad webserver config... should be fixed now) > Don't require users of your API to start goroutines to use your API correctly. Actually, what I postulate in the article is different... The theory is that making the caller kick off the goroutines puts more control over concurrency into the hands of the caller, and the resulting API is simpler. > Avoid high goroutine fanout in your implementation. That's for sure. :)