Rust doesn't really have a business case outside of extremely niche things. Its still mostly an academic exercise, similar to what Haskell was/is. Even in perfo

Rust doesn't really have a business case outside of extremely niche things. Its still mostly an academic exercise, similar to what Haskell was/is. Even in performance or embedded devices, its not really preferred. The issue with Rust is that most of the algorithms that you commonly write in code don't really benefit from memory safety that Rust offers, and not having to write explicit code in a language like Python is much simpler and faster. As for performance stuff, its often much simpler to encapsulate the code that needs to run fast in a system library and interface to it through native bindings in higher level language. Rust is good for writing native performant applications that need to run and not crash. For example, writing an autopilot/stabilizer for a drone - you need to have it be able to interface with other software, like motor controllers and data coming from the communication chip, at the same time while performing computation, storing stuff in memory, e.t.c. Rust is a very good choice for this because it will reduce the chance of errors due to memory conflicts.