> and it’s not what you’re interested in doing if you actually want to take advantage of hardware threads. This is not always correct. Coroutines don't necessa

> and it’s not what you’re interested in doing if you actually want to take advantage of hardware threads. This is not always correct. Coroutines don't necessarily have to be the only mechanism for splitting work within an application. A master process can distribute work among several worker processes that then use coroutines internally. This still takes advantage of hardware multithreading capabilities with a low number of separate processes and then further splits the work up on several coroutines in each thread.