I speculate it goes this way: 1. Some people at a Java company get excited about Rust 2. They write some microservices in Rust. They're now having "Rust jobs" 3

I speculate it goes this way: 1. Some people at a Java company get excited about Rust 2. They write some microservices in Rust. They're now having "Rust jobs" 3. The company hires more Java devs to replace the people that now maintain the Rust side of things 4. When in need there are internal shuffles to replace those Rust devs It can't go forever, but as far as I can tell the usage in corporate has started not long ago. You'll have Rust jobs, but they'll be the same shit as Java jobs. There was a study done like a year ago that showed across the board decline in developer satisfaction with all the "new and shiny" JS frameworks. I 100% think that when companies will inevitably start hiring people to maintain those legacy Rust "internal sideprojects" the same will happen. It is when a not driven by passion workforce, people who complete taks and features instead of doing the "provably correct thing" have a go that technologies get vibe checked. We will see which way it goes.