Why would GC drop calls? I know a few high volume networks using .Net based platforms without any issues, Go would run circles around them performance wise.
.NET GC is pretty configurable though. I don’t know about the Go one.
.NET's GC is faster than Go's GC. They had a big head start.
Yes, both unbound heap allocation times and GC pauses could stall and cause critical timing failures. But you could theoretically use these features in a system designed for low latencies.
Go is known to be quite usable a server programming language (Caddy is a well-known HTTP server written in Go), so I think the language choice is quite fit. You wouldn't say a HTTP server drops requests because it has GC / uses Go, so why would it drop calls?
Why would it? It feels like you're making assumptions about a lot of things.
Last I remember, mobile signalling had quite strict timing requirements.
Go's GC supposedly never runs longer than 1ms, so no.