Skip to content

Comment on Go vs. Rust: Writing a CLI Toolparent

Comments

My experience is completely the opposite.

Go is excellent for cross-compilation. The same compiler can compile to a lot of platforms out of the box, and making portable applications requires very little to no platform-specific code. Go's standard library exposes a consistent API across all platforms, and external dependencies also do a really good job at this.

Rust, on the other hand, requires installation of subsystems, and only few of them are properly supported ("Tier 1"). Even a common target such as linux/arm is constantly broken. Dependencies, including popular ones such as libc, are incomplete and not really tested on systems that are not linux/windows/macos.

Even on these 3 platforms, writing portable code requires a platform-specific code.

Please file bugs for linux/arm! ARM themselves are in the middle of getting it promoted to Tier 1.

Dependencies, including popular ones such as libc, are incomplete and not really tested on systems that are not linux/windows/macos.

That is a consequence of a thin standard library, no guaranteed support on all platforms that the compiler targets.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.