I know plenty of senior C++ devs who would love to use Rust professionally. Maybe most Rust jobs simply fill easily internally and don’t get reach the public?
Which validates the authors point - it can be hard to find or get a job writing rust. Much more so than other languages. Even if there technically are jobs around, just knowing rust wont help that much in obtaining one.
Perhaps but it’s also a subtle but important distinction between “there are no Rust jobs” and “there are no open Rust jobs”. The former implies it’s a dead end skill set while the latter implies potential openings in the future. It may just be one of those things where you need to keep your ears open for openings and jump on one when you see it. Personally I think Rust is just getting started and there will be a ton of job opening’s, just maybe not for a little while longer.
Neither OP nor I claimed that. Only that it is hard to find a job in rust or that knowing rust will not help you get a job today (more so than any other language that is). I do also think that rust has a bright future - but as things stand today it can be hard to get a rust job (at least ones that are not just for cryptocurrencies/blockchain). And it could take 5 or more years for significant change in that area.
What was claimed is that you can’t get a Rust job which implies there are no Rust jobs, so it’s important to call out the distinction. This was further implied by the tone of the article title which implied that the author was leaving Rust for good. While the contents of the article was more nuanced the title counts for a lot and has to be taken into consideration.
On the whole cryptocurrencies/blockchain jobs thing I’m not even sure I’d consider those real jobs. The overwhelming majority of those are startups that pay in equity and I expect nearly 100% of them to fail making that “equity” utterly worthless. I’d only consider positions in established companies paying actual salaries as real jobs.
Some do. But introducing new language to a team is non-trivial. And maintaining a project in more than one language has its own challenges. Rewrites of course are risky and expensive. So, Rust tends to get introduced very incrementally, for smaller projects, or for green field dev. Look at all the drama in the Linux kernel.
I know plenty of senior C++ devs who would love to use Rust professionally. Maybe most Rust jobs simply fill easily internally and don’t get reach the public?
That’s my guess. All the openings are being filled internally and never even make it to public listings.
Which validates the authors point - it can be hard to find or get a job writing rust. Much more so than other languages. Even if there technically are jobs around, just knowing rust wont help that much in obtaining one.
Perhaps but it’s also a subtle but important distinction between “there are no Rust jobs” and “there are no open Rust jobs”. The former implies it’s a dead end skill set while the latter implies potential openings in the future. It may just be one of those things where you need to keep your ears open for openings and jump on one when you see it. Personally I think Rust is just getting started and there will be a ton of job opening’s, just maybe not for a little while longer.
Neither OP nor I claimed that. Only that it is hard to find a job in rust or that knowing rust will not help you get a job today (more so than any other language that is). I do also think that rust has a bright future - but as things stand today it can be hard to get a rust job (at least ones that are not just for cryptocurrencies/blockchain). And it could take 5 or more years for significant change in that area.
What was claimed is that you can’t get a Rust job which implies there are no Rust jobs, so it’s important to call out the distinction. This was further implied by the tone of the article title which implied that the author was leaving Rust for good. While the contents of the article was more nuanced the title counts for a lot and has to be taken into consideration.
On the whole cryptocurrencies/blockchain jobs thing I’m not even sure I’d consider those real jobs. The overwhelming majority of those are startups that pay in equity and I expect nearly 100% of them to fail making that “equity” utterly worthless. I’d only consider positions in established companies paying actual salaries as real jobs.
If they’re seniors then why not slowly introduce Rust to their existing codebases?
Some do. But introducing new language to a team is non-trivial. And maintaining a project in more than one language has its own challenges. Rewrites of course are risky and expensive. So, Rust tends to get introduced very incrementally, for smaller projects, or for green field dev. Look at all the drama in the Linux kernel.