Go is notoriously slow moving and very conservative feature-wise. Can you actually point to anything specific about Go and say "Go only has that because they ha

Go is notoriously slow moving and very conservative feature-wise. Can you actually point to anything specific about Go and say "Go only has that because they have more contributors"? Anything more specific than "Google is richer, checkmate"? Note that I didn't say that Rust was buggy or was too small or something like that, I said that Rust was too complex and it didn't allow integration into external build systems. Both are things that the Rust project is completely capable of addressing but has chosen not to prioritize in favor of other language features. Correct me if I'm wrong, the earliest discussion I can find about meeting large org requirements took place in 2019 [1], 8 years after it first appeared, or 3 years after v1.0. It's their choice what to do and when to do it, but I think it's misleading to perpetually point at Google and ignore the Rust project's priorities. I'm open to a better explanation as to how Rust is somehow production-ready and extremely well known but comparatively few professionals actually choose to use it. [1] https://users.rust-lang.org/t/rust-in-large-organizations-meeting/32059 https://users.rust-lang.org/t/rust-in-large-organizations-me...