I feel that you just need to accept the fact that you have no idea what America is. There are 300 million people who live here but you act like you're a tourist who landed in Las Vegas and thinks that the whole country is apparently really obsessed with slot machines and topless bars. I can't really change what you prefer but I assure you that there are plenty of us here who do not care for your circles where apparently everyone curtsies at each other.
ISRG is wrong too, definition-wise. Go is not memory safe. It is much safer, and I wouldn’t fault you for taking a C codebase and porting it to Go to avoid memory safety problems, but that does not make it memory safe in the same way Rust et al are memory safe. This is the same way that MTE does not thwart all memory corruption but it stops a lot of them. I accept your premise that Go has brought memory safety over the line to where it is apparently easier to find logic bugs than exploit memory corruption, which is laudable since C(++) has never been able to do this and likely never will, but in line with the pedantry that started this whole chain of comments, it’s not memory safe.
Most of the fastest inference and training code in production today is written in Python. There are no global locks on the GPU except the ones you put there
These days GCC has much better error messages even for non-vector code, IMO. I feel like Clang has become more of a research platform and GCC is winning on the usability front