> In the videogames world we [...] don't care about memory safety (not an issue)

Well, that's how you get remote code execution vulnerabilities in CS:GO [1]. If you're doing anything at all over the network you absolutely need to care about memory safety. This doesn't mean that you need to use Rust of course, but security is still an issue.

[1] https://hackerone.com/reports/351014

I see this claim a lot, but I don't remember the last time I played a game with no network access. If you're capable of opening ports to the mad world of the internet, I think memory safety is relevant. But I'd love to be educated on why this is wrong.

It has improved a little a while ago with the stable profile overrides feature, allowing you to compile dependencies in release mode and your own logic in debug mode. Made work on my Rust written game much easier. But there's still ways to go. Ideally you have an engine and lua/scripting layer anyways.

You should care about memory safety in any language. The point is to reduce bugs and have more maintainable code, that doesn't introduce memory errors when something is changed. Or when making something concurrent.

Now of course if you use a garbage collected language, then you aren't in control of memory, so it's less of an issue. But if you are using C++ for high performance applications such as gaming, then you are in control of it and need memory safety.

Why don't we care about memory safety?

We care about memory safety as much as any program. Engine code doesn't need fast compile times, scripts do, but they are scripts.