> User-space network driver? The benchmarks group Go closer to Rust with Java / C# way behind
That's a very generous reading of those benchmarks. What you said is true in the latency benchmarks, but in the throughput benchmarks, C# _beats_ Go at high packet rates and is much closer to Go than Go is to Rust at low to medium packet rates.
Re:Why Go and Not Rust?
by loonyphoenix on Monday September 16, 2019 @11:14AM
(#20984877)
How do you get that C# is way behind Go on this one? If anything, those benchmarks show these groups of languages performing at roughly the same level:
1. C/Rust
2. Go/C#
3. Java/OCaml/Haskell
4. JavaScript/Swift
5. Python
I agree that my wording is too strong due to my memory of the latency results. As you increase the load, Go is closer to Rust/C than C# (see last benchmarks) and at a given load, C# isn’t in picture. It’s fair to say that Go/C# is similar while Java is far behind depending on the benchmarks that are important to you.
Re:Why Go and Not Rust?
by joelfolksy on Monday September 16, 2019 @06:09PM
(#20989044)
> and at a given load, C# isn’t in picture
And depending on how you draw the picture, Go might not even be in the bandwidth picture.
User-space network driver? The benchmarks group Go closer to Rust with Java / C# way behind: https://github.com/ixy-languages/ixy-languages
This would be a very complex comparison and simple analogies do us a disservice. I think the author's blanket statement that Go is faster than Java / C# also seems too broad.