In theory, practice is like theory. In practice, it isn't.
Maybe in 20 years, JITs can provide AOT-like throughput without significant memory / power consumption. Not with current tech, except on cherry picked benchmarks.
In theory, practice is like theory. In practice, it isn't.
Maybe in 20 years, JITs can provide AOT-like throughput without significant memory / power consumption. Not with current tech, except on cherry picked benchmarks.
https://devblogs.microsoft.com/dotnet/grpc-performance-impro...
Or this one where JIT compilers beat Swift?
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..
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.
This only affirms our point that JIT can keep up with, or beat, AOT already.
As for non idiomatic code, that is even worse for Go code, as it lacks many of the performance tuning knobs.