Rust should make the pool of C++ developers decrease exponentially in the coming decades. There's little reason to code a greenfield project in C++ unless it involves leveraging some niche libraries, and those niche libraries will eventually have Rust equivalents.
Or be a part of a discord group that flies a pride flag in your face for 6 months of the year. A helping of ideology is what I've really been looking for in a programming language.
I wrote several hobby projects in scala but once I realized what kind of people were in that community I decided not to have anything more to do with it. (And I'm not talking about Tony Morris)
May not be rough for me, but it's rough for @ChoooCole. You're being dismissive, acting like the ideology is harmless. She has to live with the consequences of the actions that the pride community influenced her to take at 16. It's not harmless.
Hmm, I think that's a little heavy-handed. Just off the top of my head: CUDA (maybe other gpgpu stuff too), gamedev, most projects with a UI. The tooling you'd be using in those spaces is still bleeding edge; too much so to use with a greenfield project that you intend to put in production, imo.
I guess you said "in the coming decades," which might be true, but for the time being it's more than just niche libraries that might push one to use C++.
There's much more reason to do a greenfield project in C++ than Rust - experienced C++ hiring is still considerably easier! Not everything has a purely technical motivator.
> experienced C++ hiring is still considerably easier
Perhaps, but you can take experienced devs with a background in other languages and expect them to write solid Rust code. You probably only need to hire 1 or 2 people who already know Rust.
I don't know any people who program in Rust. I've been programming 25 years professionally. On my LinkedIn and through friends I probably know 50 people who do c++ programming in some capacity, including myself, to a poor level.
As someone who only knows C++ to a poor level, you’re exactly the sort of person I wouldn’t want to hire for a C++ job, but I would consider hiring for a Rust job. The bar is way higher for C++ because it’s so easy for even experienced developers to introduce mistakes.
I'd be tempted to pick Rust for a greenfield project even if I had only a team of C++ devs with no prior Rust experience. Having one person that can teach it would help, but it's not an absolute necessity. And luckily every team has that one person ho is the Rust evangelist...
If you can program C++ you'll pick upp Rust more quickly than any other convert. Unless it's a startup with a short runway where you might not have the luxury of a slower start, then I think it would probably pay of in both productivity, staff retention, ease of recruiting (later), and a lot of other parameters.
I'd say the trend in the industry is to hire engineers rather than language specialists. An experienced C++ guy should be able to learn the Rust basics in a few months.
If you're writing a GUI app, you usually don't need the exceptional efficiency that is C++'s selling point, so you are probably better off using Swift or C#, instead of either C++ or Rust.
Claims like these always reduce C++ to a systems programming language, neglecting the fact that is primarily used in computationally expensive projects in which Rust cannot be a valid substitute.
