I downvoted your "+1" and "TY" comments because they add nothing to the discussion -- just upvote instead of leaving such comments, this isn't Reddit (yet). Complaining about downvotes is also a good way to get more downvotes. Your original comment was probably downvoted since it's not very constructive either, it's just a random thought that entered your head (it's not a terrible thought, performance is something to be considered if you're seriously going to look over the pragmatics of using a random language), and it didn't really deserve to be a comment. A better comment that would have received upvotes would have been to run your own benchmarks and report the result instead of pointlessly wondering in public. (Or as the question can come across, demanding someone to do the benchmarking for you as presumably you searched for one before making such a demand.)
Which, I think, misses the point. Unless your Go program is currently not fast enough, why would you consider a port? And, if it isn't fast enough, are you sure you are using the appropriate algorithms and tools for the job? It may be that Go isn't the right language, but I would think long and hard before a re-write from any language to any language, unless it's a toy project (in size, not importance), in which case, you could rewrite it and find out in a day or two and it might be a fun experiment worth writing about.
And, lots of benchmarks between C and Go have already been done. Likewise, Rust and Go, and Rust and C.
Comments
I downvoted your "+1" and "TY" comments because they add nothing to the discussion -- just upvote instead of leaving such comments, this isn't Reddit (yet). Complaining about downvotes is also a good way to get more downvotes. Your original comment was probably downvoted since it's not very constructive either, it's just a random thought that entered your head (it's not a terrible thought, performance is something to be considered if you're seriously going to look over the pragmatics of using a random language), and it didn't really deserve to be a comment. A better comment that would have received upvotes would have been to run your own benchmarks and report the result instead of pointlessly wondering in public. (Or as the question can come across, demanding someone to do the benchmarking for you as presumably you searched for one before making such a demand.)
I'm actually very curious... I have a few project in golang and if this was more performant I would consider porting them.
Which, I think, misses the point. Unless your Go program is currently not fast enough, why would you consider a port? And, if it isn't fast enough, are you sure you are using the appropriate algorithms and tools for the job? It may be that Go isn't the right language, but I would think long and hard before a re-write from any language to any language, unless it's a toy project (in size, not importance), in which case, you could rewrite it and find out in a day or two and it might be a fun experiment worth writing about.
And, lots of benchmarks between C and Go have already been done. Likewise, Rust and Go, and Rust and C.