@worldsendless the main win is just async dispatch, really. anything that implements fibers/green threads on top of an async dispatcher to wake them up is going to outperform anything that uses the old blocking threads model. on the plus side fibers look nicer than the callback hell of nodejs.

a long time ago there was much screaming about how the BSDs had things like kpoll and kqueue which let you pause a program until any one of a collection of file descriptors had something to read, which was instrumental in solving the c10k problem.

apple had grand central, BSDs had kpoll/kqueue. erlang channels already worked like this but most people are allergic to erlang. libuv+nodejs basically pushed async to the forefront because webshit bootcampers could use it by default (in java it's not default; you have to specifically use newio/netty/etc.)

I forget if Go does async networking. there is some machinery where a goroutine sometimes occupies a thread and sometimes doesn't, i think it may try to if it can (and fall back to multithreading if it can't) but i've been out of that game.