I love how evocative the word tornillo is. In my mind it translates as "little twisty thing".
lolcatnip
whether the software is memory safe depends on the expertise of the devs
No. Just stop. If a language depends on the expertise of the developer to be free of memory bugs, then by definition, it is not memory safe because memory safety means such bugs are impossible by design. Quit trying to redefine what memory safety means. A program being free of memory bugs does not in any way imply memory safety.
I'm very experienced with C++and I still feel like I'm juggling chainsaws every time I use it. And I've personally run into into things like use after free errors while working in Chromium. It's a massive codebase full of multithreading, callbacks, and nonlocal effects. Managing memory may be easy in a simple codebase but it's a nightmare in Chromium. Tools like AddressSanitizer are a routine part of Chrome development for exactly that reason. And people who think memory management is easy in C++ are precisely the people I expect to introduce a lot of bugs.
It's very relevant. Wars are still mostly fought by troops on the ground, and you have to be able to get them to the place you want to invade. About the only other option is to try to physically destroy a hostile country with nuclear weapons, but that's pretty much guaranteed to be disastrous for all parties involved.
*Central American prison.