They're just fundamentally for different things. For most classes of problems where the distinct features of one or the other would make any difference, if you'

They're just fundamentally for different things. For most classes of problems where the distinct features of one or the other would make any difference, if you're choosing between Rust and Go, then you may consider that you might not entirely understand either your problem and/or why either of these should be considered as part of a solution. We chose Rust for a bunch of reasons related to enabling high-assurance software development with better ergonomics & efficiency than attempting to do the same with C and bolting a bunch of disjointed augmentations onto either it or its toolchain. Substructural type system + HM type system + ease of integration into embedded targets is fantastic for the platform we're building and the markets we're addressing. Using Go would make no sense at all for us, but may be perfect for a use case where the same kinds of guarantees & assurances aren't necessary.