I agree with you. I guess the best solution would be something in between “await” and goroutine. My understanding is the main issue with “await” model is that

I agree with you. I guess the best solution would be something in between “await” and goroutine. My understanding is the main issue with “await” model is that you only abstract The Task model. Running task don’t gave a real ID and stack like “Go” and “Erlang” you can list all running fiber how much memory and CPU they use ... I believe you could write your own event loop easily in Go if they exposed the internal api used to pause and resume goroutine, you can already pause goroutine by having them wait on a mutex and resume them from your custom event loop by releasing that mutex.