Ah thanks for clearing that up. The project that my colleague switched from Go was also a low level project. It seems like Go isn't fantastic for lower-level projects yet.
About your colleague, what exactly made him/her switch?
To define a bit more what I mean by "low-level":
- I think that Go is "lower" level than Java because Go is compiled to a native executable (no virtual machine) and Go gives you control over memory layout (not everything is a reference like in Java).
- I think that C/C++/Rust are lower level than Go because you control memory allocation and deallocation (no garbage collector) and you can even customize the memory allocator if you need. It's also more efficient to interface with C libraries because the calling conventions are identical.
Unfortunately, I'm under an NDA, but I just went back in slack to see what the issue was. Seems to be that we didn't have the build process and tooling to support Go and our system is under extreme resource constraints so supporting anything outside of our existing tools is a no-go (no pun intended).
In terms of the other languages you've mentioned, I went to school and all they thought us was C++ so I'm fairly comfortable there. I still haven't used Rust, but I've touched a ton of other languages. The language I've been experimenting with the most recently is Swift since I'm an iOS developer.
