Go-lang was materialized for these kind recently, but we are left with big spaghetti of code, far from clean and good practices. Programmers spend their whole career debugging the mess or just gave up.
Rust has given what programmers and companies want, giving no one a reason to complain. Less testing, low resources costs, quick deployments is what managers want.
Will the joy of programming return?
Will the cohort of employees be thankful to each other again
will they be passionate and innovative than recklessly money-greedy or burnt out?
Will the bad codebase be a thing of the past for the community?
If they say something like "I can code just fine, I don't need rust holding my hand", I start wondering if they just don't get or don't like the whole concept of modern programming.
If someone hates rust like that, they probably think of programming as a personal challenge or achievement, where success happens through skill.
If someone loves rust, I would think they're more likely to value repeatable, scalable processes, where success comes from following a process that has robustness built in.
And of course, if they hate the idea of programming skill being made into a repeatable process... maybe they also hate software in general, since they probably prefer low tech, hands on stuff without a computer in between them and the results.
I imagine any competent coder can do rust just fine, but their enthusiasm and level of effort will be revealing. All else being equal I feel like I wouldn't enjoy working with someone who hates rust.
But I am very much not a manager, and could be all wrong in my armchair psychology. I know there are other less philosophical criticisms of rust like the small standard library and ensuing crate reliance, so some might not be on the rust train for much more pragmatic reasons that don't say as much about them as a programmer.
It boils down to skill and discipline, not the language. There is no silver bullet.