While I think that rust is a great choice, if multi platform static executables is your goal then I think you missed a language that does such a thing extrmely well. I’m surprised the author didn’t even consider Go for this purpose.
* memory safety without garbage collection,
* concurrency without data races,
* abstraction without overhead
> But at that time (early May), I was interested in learning Rust, after vaguely hearing what it provided, namely:
And then he listed what you listed in your comment.
As he wrote the main requirement was not to include JRE. This could also be achieved by using Go.
I have been responsible for building and deploying Python, JVM, and Haskell projects to production servers. For Haskell projects it was pretty much painless, Python and JVM were "challenging". The main advantage comes from having native binaries and a good build system that does the right thing, which Rust is also good at.
OCaml hits most of the boxes and would be more convenient/familiar to most users since it's strict and impure.
Rust code is statically linked by default. C code you link to may not be. Many -sys packages (that wrap C libraries) give you an option to link statically or dynamically.
libc isn't statically linked by default, so that's usually the only thing not-statically linked in a pure-Rust program. You can use musl instead if you'd like.