RexSystem1 voteoriginally by @Speykious on GitHub1 reply
Rust is less compatible than C, meaning users (such as those running BSD, plan9, etc) may be unable to run it.
Rust supports FreeBSD officially as a Tier 2 target, but what matters most in Fluxer's case for Rust used client-side is the WASM target (also Tier 2), because that's what libfluxcore compiles to. So if your platform runs a Chromium or Firefox derivative, it will run Fluxer.
https://doc.rust-lang.org/nightly/rustc/platform-support.html
If the platform is so niche that it can't run a browser, imo it's not worth supporting in the official client and you might as well write your own.
you trade performance, reliability and user trust for real-time automatic memory management
This is true of garbage-collected languages. Rust is not garbage-collected, it simply gives you compile-time rules to manage memory yourself safely, which you can extend using unsafe if you need to. The trade-off is more time spent checking the code at compile time, not runtime performance. Though the Rust compiler mostly spends time generating code and handling generics. At runtime, it is as performant as C and more in some cases.
There is no world in which C is safer than Rust. It always baffles me that people always try to attack the least attackable aspect of the language, the one that's empirically proven, when it has actual real problems that people could be talking about instead.
(I'll also note that most Rust devs don't like being associated with cryptobros, but unfortunately we're stuck with the state of the job market. It is what it is.)
Man, stop. Rust is not even sound... Rust model is broken. There are Github issues related to that. The company control is real. The language specification is non existent and there are million other issues with the language. There's no ABI, you can't make shared libraries without C. Don't tell me the opposite because I use Rust very very often. The only reason you're here is because of this:
"Member of the Rust Evangelism Strike Force. Also I hate Java"
copied right from your profile. That invalidates all your arguments. You people gotta stop with the sectarism.
Thread
Comment by @Speykious
unsafeif you need to. The trade-off is more time spent checking the code at compile time, not runtime performance. Though the Rust compiler mostly spends time generating code and handling generics. At runtime, it is as performant as C and more in some cases. There is no world in which C is safer than Rust. It always baffles me that people always try to attack the least attackable aspect of the language, the one that's empirically proven, when it has actual real problems that people could be talking about instead. (I'll also note that most Rust devs don't like being associated with cryptobros, but unfortunately we're stuck with the state of the job market. It is what it is.)Comment by @ctudor0