More suitable sure but I'm not convinced you'd want to use anything but C or C++ for a server that needs to be as "real-time" as possible.
For what value of "as possible?" It's kind of a miracle that twitch game mechanics FPS work at all with typical Internet latencies, which is one of the various reasons why I'm not doing that. "As possible" in my situation, doesn't include the resources to do that.
I wish Go could use RAII or another memory scheme so they could drop GC altogether.
There's always Rust. Also, Erlang can "cheat" at GC in some ways due to immutability. Server side Swift has potential as well.