indeed. this is one of the benefits of a concurrent sequential processing model with a scheduler. e.g., in Go, blocking syscalls get put on their own thread i

indeed. this is one of the benefits of a concurrent sequential processing model with a scheduler. e.g., in Go, blocking syscalls get put on their own thread in a thread pool, so that processing can continue while waiting. I'm sure you can do something similar in a raw event loop, but I don't think the machinery is generally baked in to the io interfaces to do so.