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.
@rumba@Croquette They’re is a lot of people scrambling to rewrite existing c projects in rust for what?
for example ffmpegs rust rewrite is slower than the c version we need more maintainers rather than creating new rust alternatives that have no purpose
@rumba making new projects in rust sure cool but when big projects that most of the world relies on etc ffmpeg crucially need maintainers and contributions rust isnt needed and is a waste of resources when C can do it better, faster and easier rust is a fast fade that will likely remain in the shadow of C. Tbh your glazing rust without looking at both sides of the argument so the picture op posted really is true
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?
@rumba @Croquette They’re is a lot of people scrambling to rewrite existing c projects in rust for what?
for example ffmpegs rust rewrite is slower than the c version we need more maintainers rather than creating new rust alternatives that have no purpose
If you want to ignore re-making things out of memory-safe technology as an advancement, we don’t really have anything to talk about here.
@rumba making new projects in rust sure cool but when big projects that most of the world relies on etc ffmpeg crucially need maintainers and contributions rust isnt needed and is a waste of resources when C can do it better, faster and easier rust is a fast fade that will likely remain in the shadow of C. Tbh your glazing rust without looking at both sides of the argument so the picture op posted really is true
Ahem…
If you want to ignore re-making things out of memory-safe technology as an advancement, we don’t really have anything to talk about here.
I know Rust superficially. I use it to create simple tests for my embedded projects, so mostly just serial terminal with keyboard inputs.
It works a lot better for me than python because Rust is a lot closer to C than python.
So I cannot comment on Rust shortcomings. I was interested in knowing for what kind of projects Rust wasn’t good.