I suspect the parent is mostly referring to Go.
Same as JARs or C/C++ binaries. You can ship the compiled product to the target runtime and expect it to launch and run as-is.
Languages with an interpreted nature require containers to also ship an additional runtime, plus a dependencies mechanism.
Which is amazing and frustrating since it exposes the inability of other languages to operate in such a simple environment. Even languages like Rust, C and C++ aren't able to do this reliably all the time, with the results being highly dependent on libraries and platforms of choice.
the Rust ppl are looking toward static linking [links]...
https://internals.rust-lang.org/t/static-binary-support-in-r... https://github.com/rust-lang/rust-buildbot/issues/24