In my job I get to speak to lots of people about Rust. Some are just starting out, some have barely ever heard of it, and then some people are running Rust silently in production at a very large c ...
No problem, I have got some prime rust inhibitor to sell you. Easy to apply and long lasting. Shame though, newly manufactured vehicles should not already rust.
I think if Rust people want C and C++ devs to switch over, there needs to be a lot more documentation that's easy to follow on how exactly to do that. For example with Swift there's an amazing tutorial called Swift for C++ Practitioners that step-by-step goes over all the equivalent functionality and how to translate existing concepts over from one language to the other. I think Swift at least has the edge there with familiarity because the syntax physically looks closer to C-like languages, so when that's not the case, even more hand-holding is going to be necessary IMO.
Automotive developers successfully switched from barely-knowing-C to barely-knowing-C++. Surely, they will be equally successful in switching to barely-knowing-Rust.
There are lots of guides, tutorials and documentation. The responsibility is no longer on someone else, it is up to the individuals to actually read any of them. And to be honest, if you are unable to use them to learn rust, maybe your c++ skills isn't that impressive either.
There are lots of guides, tutorials and documentation.
is one I found using a tool called search engine...
Strange. That’s not what I get when I search for “Rust for C++ programmers”. I get flooded with anecdotal accounts/posts from people on Reddit and YouTube talking about their love or hate towards Rust.
Then there’s 3 hour-or-longer videos about Rust which target C++ devs directly. Two are from 2022 and 2019 with one from 2023. Only the 2022 video starts from basics with features that a C++ dev would actually need to understand, like ownership, borrowing, and references. One jumps right into multithreading ideas by discussing mutex. The other jumps into how everything is made “easier” because the compile does borrow-checking instead of having the developer manage it.
These videos probably aren’t bad, but they don’t touch on the larger “gotchas” that C++ maintainers will be scratching their head at, like explicit lifetimes, inevitable headaches with error handling, and reference/target mutability. Some of them are a good start, but they mostly focus on just technical features. It’s difficult to find a resource that helps you learn how to plan out your project early on so you’re not refactoring later due to the topics mentioned earlier.
And to be honest, if you are unable to use them to learn rust, maybe your c++ skills isn't that impressive either.
And this is why 6% of non-Rust users have cited the community as a barrier of entry. Immediate pettiness and hostility rather than trying to get the best resources into the hands of newcomers.
The O'Reilly book Programming Rust is very much targeted at C++ users, even if it isn't explicitly marketed that way.
I read the first edition, which predated async Rust, so I can't comment on how the second edition handles that topic. But the handling of everything else was, I think, excellent.
It's by the Android team at Google, and while it doesn't require knowledge of C++, it seems to be intended to bring devs up to speed on the concepts required for using Rust in Android and Chromium.