> But maybe if a C++ programmer were talking to a Rust programmer or any other language with a higher level memory paradigm, and if it was a conversation about whose language was best for what, then maybe they would feel defensive and need to act a bit superior.
There is a reason "I will never be able to get the control I need (but I don't know)" or "I'll have to use unsafe everywhere (but I haven't tried)" are anti-Rust tropes. It's possible for certain game dev patterns to be awkward in Rust (really interested in hearing more about these!), but these other criticisms smell less like highly relevant informed criticism, and more like one hasn't tried Rust, as much as surface-level, mole hill criticism of hypothetical or pathological instances of bad syntax do.
It isn't that one uses raw pointers. It's much more an attitude I've witnessed in younger programmers that if they're not doing it in C/C++, they're not doing the thing. It's about vibes as much as anything else, and I think, when their heros use their own vibe-level criticisms, they only reinforce that perspective.
> Or, perhaps when you say they act big about using pointers, do you mean that they act big about using pointers safely?
No, I wasn't thinking of that, but that's another part of it. And now that you mention it, "My code doesn't have any of these issues" can be yet another defensive tact.