You keep posting a 2 year old msft blog post which is out of date. The benchmark project page they link to points to this for the most recent results: https://www.nexthink.com/blog/comparing-grpc-performance/

Note that akka is currently second for single core, and fastest with multicore. .Net has a nice result, but lets use up to date results. Especially when it still fits your argument that JIT can compete in benchmarks with suitable warmup, etc..

Maybe because I wasn't aware of other ones?

Still it confirms the point that Go isn't up to the competition, which was my point, not that .NET is the super dupper best thing in the world.

Your article shows that Java, Scala, and .NET are all faster than significantly faster than Go in latency and throughput, and can beat C++ as well.

This only affirms our point that JIT can keep up with, or beat, AOT already.

It can, after a warm-up period and by using 10x the memory and likely non-idiomatic code. Sometimes one can live with that, sometimes not.

Look at benchmark game’s java programs - it is very idiomatic compared to most other contenders yet it is exceedingly fast

Only when the users are clueless to configure JIT caches.

As for non idiomatic code, that is even worse for Go code, as it lacks many of the performance tuning knobs.

I literally said this in my comment.