I'd add to the yesterday's discussion that it might not be the best idea to use a/thread
but instead use your own thread pool of limited size. So you don't end up spawning one thread for each go block/process.
it depends
(that was wildly inaccurate)
but I am going to stand by it depends
threads are cheap, it's context-switches that are expensive, it's more important to make sure significant work happens in the thread (so the amortized cost of the context switch is lower) in most cases
but as said elsewhere, it depends
Sure, it depends. But you can create 10,000 go blocks easily but it's probably a bad idea to spawn a new thread immediately for each of them