I&#x27;ve read your replies and I think you&#x27;re arguing too passionately and missing facts.<p>It doesn&#x27;t matter that there&#x27;s much legacy C++ code. Two things will happen:<p>a) it will stay C++03, regardless of what changes in C++ or what other languages pop up. This kind of code is probably part of a working product which fulfills its mission and maybe gets small updates or fixes.<p>b) it will continue to be maintained, and it will be able to benefit from some or most of the changes coming in new C++ versions. It doesn&#x27;t mean that it will be converted to super duper C++14, but that&#x27;s not how software maintenance works anyway! And guess what, they probably won&#x27;t be converted to Rust either, but they will be better due to the new standards. You are building a strawman when claiming that it&#x27;s either Rust or failing to use pure C++14. 
Successful software tools offer backwards compatibility when making improvements and iterate instead of replacing everything. Just ask the Python and Perl teams.<p>And this is how C++ was able to build marketshare, by offering a transition path from C. What exactly is that path for C++ to Rust, rewriting everything?<p>Finally, new projects will use the new standards. My current project is C++11. The next one will be C++14 and we will absolutely make use of the new features where it makes sense.