I don't know about goroutine performance, and maybe you're right about their weight relative to modern OS threads. I'm talking about the scheduling model rathe

I don't know about goroutine performance, and maybe you're right about their weight relative to modern OS threads. I'm talking about the scheduling model rather than the specific implementations in Go and Rust. The game engine I worked predates them both, and at the time, there is no way 10,000+ OS threads could advance in every rendering frame. Just entering and exiting the kernel for each thread would take longer than the frame budget. It had to be a userspace queue.