Comment Re:Trust? (Score 1) 74
I asked ChatGPT, and it's making the same argument that I'm making: “https://chatgpt.com/share/6aa807d4-b858-83ea-8fb1-b8fe5dbb6c16”, it's memory safe, with qualification, which means it's not memory safe. The qualification point is a big point, just so we're on the same page, the problem I have with the claim of memory safety, is that it convinces bad programmers they have that safety net when they don't.
I've seen this time and time again where a language has a feature, such as “memory safety”, or “type safety”, but then the developer uses “any” instead of a type, and thinks their type safe. I had a Jr Dev submit code full of $any() in the HTML of an Angular application. He then explained to me, it was safe since Typescript has type checking, therefore, $any() is a good workaround to building a proper type and interface for what he was doing.
Either learn to program and develop code safety, making yourself the first line of defence for mistakes, and they happen, and once you're sure the code is functioning at near 100%, then you can rely on the “memory safety” or “type safety”, or “X”. The idea that Rust makes things safer or more trusted is nonsense, it might be a very capable language, but the safety, and the trust is based on the developers / engineers, not the language.
When you have to write safe code, that is used for automotive, or military, you can't use pointers, function pointers, or the cool new features of most languages. The code has to be simple, basic, and clean; otherwise they don't certify it, even if you can write the code safety, and assure all paths have full cleanup and checking being done, you still can't use pointers. Maybe this has relaxed in the last 10-years, but 10-years ago that was the standard I had to write code to, for our two military clients.