The first three paragraphs: experienced engineer, knows a few languages, still finds Rust daunting after two years, has tried to and stopped learning multiple times.
All of that for the upside of being able to look under the hood, being forced to think about data first, and the great tooling.
The effort vs. reward here is why most companies will stick to something much simpler and why Rust, for almost any given problem, there is most likely a "better" language for the job, and even where Rust shines, there will remain a more popular language for the job for some time to come.
You really have to smoke whatever quality herb they're smoking to get into it, because the rewards will take a while, if ever.
All of that for the upside of being able to look under the hood, being forced to think about data first, and the great tooling.
The effort vs. reward here is why most companies will stick to something much simpler and why Rust, for almost any given problem, there is most likely a "better" language for the job, and even where Rust shines, there will remain a more popular language for the job for some time to come.
You really have to smoke whatever quality herb they're smoking to get into it, because the rewards will take a while, if ever.