> Considering we already know how to make C/C++ programs memory safe... I think that the legion of memory bugs which still occur in C/C++ programs are proof of

> Considering we already know how to make C/C++ programs memory safe... I think that the legion of memory bugs which still occur in C/C++ programs are proof of one of two things: 1. We (the industry as a whole) do not actually know how to make these programs memory safe, or 2. Knowing how to make programs memory safe in C/C++ is not sufficient to prevent memory safety issues. Either way, it seems clear that something needs to be done and that the status quo in C/C++ programming is not enough. I'm not saying Rust will be the right answer in the end (I do like it, but there's a ton of hype and hype makes me distrustful), but I can't fault people for wanting to try something new.