1–10 of 22 posts
Not considering toolchain / language maturity & stability, what are disadvantages of rust?
To answer to your question, I will say it will take you time to understand and to be productive with Rust.
But, please stop, Go and Rust can't be compared, they don't have the same goal in mind.
- The ABI is not stable yet
- The compiler is not the fastest
- Doesn't work on all architectures (compared to C in the embedded space)
While those are potential downsides, they don't have to be. It all depends on what you're using it for and the language you're coming from. I would ignore the "learning curve" comments as they're (in my opinion) irrelevant. You learn it once and then reap the benefit for the rest of your career so a couple of months of investment doesn't sound that bad.
> Not considering toolchain / language maturity & stability, what are disadvantages of rust?
You can't really "not consider" these things - they're big factors in any decision you might want to make. If you think the Rust toolchain and language ecosystem are half-baked and not yet ready for prime time, that's quite important!
I think there is a part of criticism on Go which are not relevant. The language has been designed to be "simple" and it do the job. The latest posts on Go were only for the Karma, re-post, no new elements, no fair statements. To answer to your question, I will say it will take you time to understand and to be productive with Rust. But, please stop, Go and Rust can't be compared, they don't have the same goal in mind.
https://old.reddit.com/r/rust/comments/c0xwjd/all_i_hear_abo... > Not considering toolchain / language maturity & stability, what are disadvantages of rust? You can't really "not consider" these things - they're big factors in any decision you might want to make. If you think the Rust toolchain and language ecosystem are half-baked and not yet ready for prime time, that's quite important!
I think there is a part of criticism on Go which are not relevant. The language has been designed to be "simple" and it do the job. The latest posts on Go were only for the Karma, re-post, no new elements, no fair statements. To answer to your question, I will say it will take you time to understand and to be productive with Rust. But, please stop, Go and Rust can't be compared, they don't have the same goal in mind.
Nonsense. For _certain things_ they can't be compared, but many things they can be. If I can compare Python and Rust, why can't I compare Go and Rust?
For example, I chose Rust at work recently for a project that was previously written in Go. How do you think I made that decision if I can't compare them?
Fundamentally yes, they're different languages. But seeing as Rust is quite usable in many areas it's perfectly valid to compare them. I see this "they can't be compared" so frequently that it's comical to me. Not trying to be insulting here, it's just perplexing.
I think it must stem from back in the day when Go was "incorrectly" labeled as a Systems Language. People ended up thinking that Rust and Go were competing for the same space. That there was bound to be a winner and a loser. They can happily co-exist, they're not at war, but they can and will frequently be compared. They have a ton of overlap.
From personal experience: Our company had tailor made use-case to use Rust (switching from Python), more than Go. Experiments were performed and Rust outperformed Go in all aspects (time, CPU, memory). Everyone acknowledged but CTO (who knows C/C++ very well, he is a filesystem developer) decided to select Go. CTO was bullish on Rust to start with but developed cold-feet later. He told me that the only reason was that it is easy to train people in Go than in Rust. This one single thing trumped everything in my case. When I look back, I see his point & I respect that.
While issues like portability, eco-system, ABI stability, etc are important, these are not inherent problems with the language itself. They will get better over the time.
For me, Rust fundamentally doesn't offer anything that 1) I want and 2) Python doesn't already have. The language I want is a better version of Python, not a better version of C++.
Rust is criticized on in too, but you can't read the criticism because it's downmodded to the background color. ;) For me, Rust fundamentally doesn't offer anything that 1) I want and 2) Python doesn't already have. The language I want is a better version of Python, not a better version of C++.
Have you tried Nim? https://nim-lang.org/
Very Pythonic if you ask me.