>> Often you might be willing to trade a 10ms GC pause of Go for much lower chances of memory corruption or crashing compared to C. I believe the C/C++ develop

>> Often you might be willing to trade a 10ms GC pause of Go for much lower chances of memory corruption or crashing compared to C. I believe the C/C++ developers will look for a Rust-like solution(even if I don't like Rust) rather than Go if crashing is an issue. Go doesn't solve the crashing issues. It has its own crashing issues(e.g. dereferencing nil pointers , deadlocks, data-races, nil and nil interfaces etc). If the GC is not an issue they can choose any other GC language so Go is not that special anymore in this regard. The truth is that Go has its own niche and that's web services.