Programming-Language-Benchmarks VS rust-csharp-ffi

The benchmark available at https://programming-language-benchmarks.vercel.app/ demonstrates that Golang stands out as one of the most memory-efficient languages presently available. This achievement is attributable to several inherent features of Golang, such as its static typing, robust garbage collection system, and the inherent structuring of data within the language. These traits collectively contribute to Golang's exceptional efficiency in terms of minimal memory consumption compared to other languages.

I found Zig implementation of json parsing is interesting. The code is free from hidden control flow !.

https://github.com/hanabi1224/Programming-Language-Benchmark...

I think https://programming-language-benchmarks.vercel.app/ is a good starting point to compare languages and compilers, also implementations are optimized for the specific language so you don't end up with a poorly ported c++ implementation in rust and wonder why it performs so bad.

It varies a lot depending on what the code consists of, but if you want concrete numbers for certain benchmarks, this site might be of interest: https://programming-language-benchmarks.vercel.app/

There is not "one real" benchmark. In the end, all you can do is test languages for a specific feature / purpose. You can see how many different suggestions people have here, and here (I think) you can see the difficulties of comparing languages. That site uses quite a lot of algorithms / problems with multiple inputs, single and multithreaded, with different optimization flags (where applicable) and so on paired with different languages, and it's a mess. Sometimes one language is on top, sometimes another. (I mean, python will very rarely beat pure C, but I wont rule out that someone already created an edge case just to refute exactly this point)

Hello, World!: Elixir vs. Go vs. Rust

Personally, this is our last year internally we will allow hand-optimized code to not be Rust (ie, no new C/C++/ASM/etc) within our C# code bases. Any new code which we need to use native for will be Rust, existing if we have to update it (more than minor bug-fixes) we will uplift to Rust. Previously it was all a bit hand-done (separate compilation, bindings etc), but example projects like this were a great help on setting up the MSBuild targets/configs.