3 ms·

> The Go vs Rust narrative seems to have thankfully mostly gone away I am not aware of that. Has something changed recently? Though IMO Rust's strength could l

• kibwen 10y ago
  "Go vs. Rust" was initially only a thing because 1) Google initially positioned Go as a systems programming language, 2) early prototypes of Rust were very Go-like (with both a garbage collector and segmented stacks), and 3) web developers who were already used to seeing Chrome vs. Firefox found it an easy conceptual extension. But Go hasn't been marketed as a systems language for a long time and Rust removed all its Go-like features years ago; the "Go vs. Rust" that we still see is just residual fallout.
  • notheguyouthink 10y ago
    It's funny, as a Go and Rust fan, they're still in the same space to me conceptually. I'm sticking with Go at the moment because moving my shop to Rust is quite difficult (for varying reasons), and because Go offers a nice compromise on ease and power. However i miss no-null types so bad. All that compile-time information is amazing. I really hope Go adopts some features from Rust.