4 ms·
People have written and continue to write secure C code, and insecure code in “safe” languages. I have written systems in memory safe languages. The languages
by hedora 8y ago
People have written and continue to write secure C code, and insecure code in “safe” languages.
I have written systems in memory safe languages. The languages that provide memory safety also incur GC pauses, which means they’re unsuitable for applications where latency matters at all. (I’ve also noticed that programs written by professionals in memory safe languages tend to have many more serious high-level bugs than those written in C/C++, but I don’t have data to back that up.)
- pjmlp 8y agoYeah, but I do have data to back up the fallacy of the perfect C programmer that writes secure C code. https://www.cvedetails.com/vulnerability-list/opmemc-1/memory-corruption.html https://www.cvedetails.com/vulnerability-list/opmemc-1/memor... Apparently reviewing code before merging into mainline isn't of much help, but lets keep this myth of secure C code alive. Σ (Logic errors in safe language) < Σ(Logic errors in C + Memory Corruption in C)
- icebraining 8y ago> The languages that provide memory safety also incur GC pauses This is incorrect, you can have memory safety without a gc. An example is Ada, and more recently Rust.
- com2kid 8y agoIIRC memory safe Ada doesn't allow for deallocation. Kinda sorta cheating. ;)
- pjmlp 8y agoIt does via memory pools, RAII (aka controlled types) and dynamic stack allocation.
- com2kid 8y agoIt isn't truly safe like Rust, as Ada can still have dangling pointers laying around, the free function is called "Unchecked_Deallocation", not sure if newer Ada has any mechanisms for better ownership semantics.
- comex 8y agoAnd Swift, which uses automatic reference counting instead of GC. This is not a “zero-overhead” design like what Rust aims for; sometimes it has quite a lot of overhead. But it is free from the phenomenon of GC pauses.
- icebraining 8y agoWell, in that regard, so is Python; the GC is only used to resolve cycles, and can be disabled.
- pjmlp 8y ago> But it is free from the phenomenon of GC pauses. Not really. RC algorithms can lead to stop the world in cascade deletion of highly nested data structures, and even cause stack overflow due to destructors being called.
- baby 8y ago> People have written and continue to write secure C code, and insecure code in “safe” languages. No. It's the inverse. People who are very good with C continue to have vulnerabilities in their code. Why? Because C.