Comparing Nim and Rust Compiled Application Binary Sizes!
Compiled software application binary size is not a CONCERN for many programmers.
When storage is measured in TERABYTES then sometimes there is the luxury of ignoring even a GIGABYTE of usage.
But that is not the world that ALL programmers live in!
Storage space can be so LIMITED for some embedded programming applications.
Great CARE must be taken to use space wisely.
Today I have seen a comparison of Rust and Nim binary sizes.
For those not in the know, Nim like Rust is an EMERGING programming language.
The Nim binary sizes are found to be SMALLER than the Rust binary sizes!
While this binary size comparison is not as SCIENTIFIC as I would like to see, it still makes me ask QUESTIONS.
What is the CODE that is being compiled?
Are these findings showing a REPRODUCIBLE phenomenon?
Are these findings showing where Rust can be IMPROVED?
Is there deeper UNDERSTANDING that we can learn from?
This is an issue that I would find to be most INTERESTING if a Rust expert weighed in!