cross VS sabinokaku

The -musl targets for Linux make it easy to dodge the need to compile against the oldest glibc you want to support if your project is pure Rust and cross is a Docker wrapper which aims to make cross-targeting in other scenarios as easy as with Go.)

...though, funny enough, if you have enough experience with Rust to not get bogged down in the details and you use cross to work around Rust's "take your time but get it right" approach to cross-building, Rust is often better at little CLI tools, purely because of how valuable it is to be able to teach the type system to check so many invariants at compile time.

Another thing to keep in mind for if just using the musl target with your usual setup is insufficient (eg. if you need to use a crate like ttspico which statically links some C code) is cross, which makes it really easy to use Docker to build and run tests.

For example, here I've hooked into __libc_start_main as part of an injector that injects the .NET runtime into a running process' address space. I could have done this with C or C++ with a little bit less safety and some more annoying package management, but I'm not aware of any way that Go gives me such low level access. And of course firing up the Go runtime within an existing address space when its only job is to launch another runtime is a bit of a dealbreaker here as well.