> In fact for me the only benefits of Go are single binary and startup time. I hope you mean "compilation time" or "time to first prototype". My experience has

> In fact for me the only benefits of Go are single binary and startup time. I hope you mean "compilation time" or "time to first prototype". My experience has been that, if a Rust binary doesn't start instantly, it's the fault of a specific library, not the language in general. Also, they ARE working on single-binary deployment for Rust... they just have a much more "Take your time and do it right. Don't hack around ecosystem flaws" approach than Go. If you're not cross-compiling/cross-deploying, Rust is already on par with non-cgo Go... you just need to use a musl-libc build target for Linux, specify RUSTFLAGS="-C target-feature=+crt-static" for Windows, etc. to get statically linked libc. (The musl-libc targets are a simple `rustup target add` away if your only C dependency is the libc itself.)