We're choosing Rust, and not Go, C++, or Node.js
Er...<p>&gt; <i>Code written in Node.js and Go could be made memory-safe with enough work, but they&#x27;re both GC based, which inevitably leads to engineers easily missing memory safety issues</i><p>And here I was (maybe naively) thinking that a garbage collector ensures memory safety? Unless they mean memory leaks (of the kind where memory is allocated and can&#x27;t be freed by the GC, but is also not used?!). But that should be relatively easy to catch with a profiler? Maybe some more explanation would have been in order here...<p>More generally, glad to see Go got 80% compared to Rust&#x27;s 90% - just hoping they weighed their priorities correctly, otherwise who knows, with such a small difference Go might have come out on top...