> A major pain point probably is that people never really followed the "conventions" of C++ resource management as rigidly as Rust enforces them. That's exactl

> A major pain point probably is that people never really followed the "conventions" of C++ resource management as rigidly as Rust enforces them. That's exactly right. Rust does a great job moving idiomatic C++ best practices into the type system and actually forcing you to do it "right". And alot of the early pain people run into when switching to Rust is learning how to do this. I suspect very experienced C++ programmers have alot less challenge getting spun up on Rust. It's sorta front-loading the pain of discovering and learning C++'s best practices. As a side effect, though, it means alot of Rust evangelism misses the mark as it mostly reveals their own C++ weaknesses (this is, on a different level, an indictment of C++, and its learning curve, but not really in the ways the evangelists often believe).