Oh, i have to try these out to see if it effects my development cycle. I do notice that cargo check is super fast, but cargo build takes a long time. So codegen and linker could be the source of slowness.

For a clean build: number of cores (because cargo builds each crate dependency in a separate process), for a build of your crate only: single core perf.

Ok, I wasn’t clear: you can now run a single compiled binary on multiple platforms/architectures/operating systems.

But yea, rip performance, probably.

Well the jar does run on multiple platforms now.

Isn’t github used only as the auth provider? It is not using any git features, just leaning on the security guarantees of github. I don’t find this too alarming.

If you want, you can use git links when declaring dependencies in Cargo.toml. So alternative to crates.io is basically any git host already!