A user asked: Is Rust worth investing in as a skill like retirement insurance?
My answer:
Unless you are working on low-level tools, kernel modules, drivers, etc., where performance is critically important and you do not want runtime garbage collection to interfere with performance, and the requirements are fixed in direction.
Otherwise, I do not recommend learning Rust.
Static strong type inference languages can be too disruptive to thinking in many application scenarios where the direction of requirements changes.
The overall direction of software engineering and the flow experience are very important; use the appropriate language for the appropriate scenario.
Do not learn Rust out of fear of falling behind; software engineering is just a tool, while thought and cognition are the true abilities.