That is a good post and a valid criticism. I'd say the more important concern with c# is to be careful you're not accidentally calling a "really blocking" func

That is a good post and a valid criticism. I'd say the more important concern with c# is to be careful you're not accidentally calling a "really blocking" function from an async method, or you will lose scalability. The lesser issue is the mundane task of changing all your function signatures in the chain to async. I too would use Go if it didn't regress in every single area for me, other than concurrency, and make me sad.