Rust isn’t as rapid as other options, has less library support, and porting existing code is relatively difficult.
IMO because of the workarounds you need to do to handle the memory safety, you end up with a lot more hard to solve bugs than you do with conventional languages. It should be noted however that the bugs don’t end up being security vulnerabilities like they do in conventional systems.
If you have something that needs to be structurally sound and/or you have enough talented people willing to work on it, it’s a great option. If it needs to be fast and cheap and you don’t have a gaggle of rust developers on hand and it’s already written in another language, it might not be the best solution.
Rust provides safety and protection.
Rust isn’t as rapid as other options, has less library support, and porting existing code is relatively difficult.
IMO because of the workarounds you need to do to handle the memory safety, you end up with a lot more hard to solve bugs than you do with conventional languages. It should be noted however that the bugs don’t end up being security vulnerabilities like they do in conventional systems.
If you have something that needs to be structurally sound and/or you have enough talented people willing to work on it, it’s a great option. If it needs to be fast and cheap and you don’t have a gaggle of rust developers on hand and it’s already written in another language, it might not be the best solution.
I come from embedded C, so what you describe doesn’t feel alien to me (minus the security vulnerabilities haha)
I much prefer working with Rust restrictions than a higher level language without hard types because I am used to it.
Do you think Zig can be a complement to Rust in cases where the language cannot solve problems?