3 ms·
Just like writing memory safe code in C is a skill issue right? ;) (I write mostly C code myself, but I'm also not immune to f*cking up now and then even thoug
by flohofwoe 2y ago
Just like writing memory safe code in C is a skill issue right? ;)
(I write mostly C code myself, but I'm also not immune to f*cking up now and then even though I write code for decades now).
- dapperdrake 2y agoASCII NUL terminated strings and double free don’t sound quite the same as gauging hardware requirements. Either you need a certain amount of memory or you don’t.
- writebetterc 2y agoYou sure can write C which makes you less prone to making memory safety mistakes, yes. Knowing how to do that is a skill issue. As you say, sometimes our skills fail us, and that's where tooling comes in. ASan, borrow checker, whatever. There's a reason that a lot of Rust programmers find their programs filled with Arc<Mutex<T>>. That's because they didn't have the skills to write memory safe systems programs in the first place. To be clear, of course I'm also not immune to fucking up :-).