4 ms·

logic bugs + UI bugs + performance bugs < logic bugs + UI bugs + performance bugs + memory bugs Just in this thread stats about memory bugs being 70% of CVEs i

logic bugs + UI bugs + performance bugs < logic bugs + UI bugs + performance bugs + memory bugs Just in this thread stats about memory bugs being 70% of CVEs is presented, so why do you believe "being memory safe doesn't get you much" ? I am not a Rust fanboy and would rather use a GCed language for most work. But I don't get this stubbornness towards progress and better tools. If some tool can make "your" life easier in many ways, use it for your own profit !!

la_barba 7y ago
Well, I'm not opposed to it, as much as I have yet to "see the light". I think that the the original non-trivial problem of deciding which thread or which subroutine gets to change what piece of memory at what time is still there. The original problem was a logic bug, but it manifests as a memory bug in C. As an aside, I've recently been working with PLCs and I've come to respect a lot of the design elements of things like the Siemens GRAPH language which makes it easy to capture my intent for sequential control stuff.