Rust vs C Pitfalls
If you&#x27;re fighting, you&#x27;ve lost. The way to convert everyone to Rust you need to be better the the competition. Not just better as in &quot;look at my features that will make your code safer&quot;. People may see the value but think &quot;I get on just fine without the borrow checker so it isn&#x27;t <i>too</i> important&quot;. You need to be far better then the replacement by providing the following:<p><pre><code>   * Great Tooling ( IDEs )
   * Great Libraries ( Everything and a kitchen sink )
   * Better Documentation
</code></pre>
Anything that can be done easily in C or C++ will need to be easier in Rust for everyone to move. No amount of language features will pull people who are doing well at their job, currently building everything they need to, and who maintain low level systems. You have to be able to entierly replace the old systems in a completely feature-complete way that&#x27;s also easy to migrate to.<p>Blog posts wont pull me away from C, tooling and docs will.