←back to thread

Embedded Rust in Production?

(blog.lohr.dev)
205 points michidk | 1 comments | 14 Oct 24 06:06 UTC | HN request time: 0s | source
Show context
culebron21 ◴[14 Oct 24 08:15 UTC] No.41835370[source]▶
The author complains there are few developers available to maintain Rust code.

I see very few job postings, and almost all of them are either cryptocurrencies (I don't want to waste my life on this), or "3 years professional Rust development in production" (disqualifies self-learners).

Given that nowadays most applications are not replied, it makes little sense to spend time even browsing the postings.

replies(4): >>41835434 #>>41835586 #>>41835927 #>>41841056 #
rapsey ◴[14 Oct 24 08:25 UTC] No.41835434[source]▶
There really is a strange dichotomy. Plenty of Rust developers have trouble finding jobs and apparently companies have trouble finding Rust developers.
replies(4): >>41835490 #>>41835491 #>>41835999 #>>41837037 #
1. Seattle3503 ◴[14 Oct 24 10:06 UTC] No.41835999[source]▶
As someone who has been searching for a Rust job lately, few rust roles are only Rust. Many are Rust + another niche domain.

- Must have 5 years of Rust and 8 years of embedded experince

or

- Must have 5 years of Rust snd 10 years of writing SQL engines.

or

- Must have 2 years Rust experience and 5 years with Linux kernel development.

etc...

If you are looking to hire someone with specific domain experience, it makes more sense to compromise on the Rust language side of things. A developer can learn Rust on the job, but it is harder to learn to write a production SQL engine on the job. But that means you aren't hiring Rust devs.

Developers who just specialize in Rust are behind their peers who are domain experts when it comes to looking for a job.

IMO that means Rust will "win" not when a bunch of undifferentiated developers learn Rust, but when the domain experts learn Rust. e.g. Kernel maintainers.