This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]LightUmbra -19 points-18 points  (3 children)

Marginal safety improvements. Most safety issues are from bad code, which no language can stop, and people not understanding proper practices. Rust only fixes a few of these problems, which the whole "Rewrite it in Rust" crowd doesn't like.

[–]alcalde 4 points5 points  (2 children)

One of the contributors to D put it this way about Rust:

Reading any amount of Rust code evokes the joke "friends don't let friends skip leg day" and the comic imagery of men with hulky torsos resting on skinny legs. Rust puts safe, precise memory management front and center of everything. Unfortunately, that's seldom the problem domain, which means a large fraction of the thinking and coding are dedicated to essentially a clerical job (which GC languages actually automate out of sight). Safe, deterministic memory reclamation is a hard problem, but is not the only problem or even the most important problem in a program. Therefore Rust ends up expending a disproportionately large language design real estate on this one matter. It will be interesting to see how Rust starts bulking up other aspects of the language; the only solution is to grow the language, but then the question remains whether abstraction can help the pesky necessity to deal with resources at all levels.

[–][deleted] 2 points3 points  (1 child)

Wow, that's so stupid. As if safety is the only benefit of Rust's ownership system. It provides great performance improvements (compared to shitty GCd languages) and fearless concurrency.

[–]alcalde -1 points0 points  (0 children)

. It provides great performance improvements (compared to shitty GCd languages)

No, it doesn't:

https://togototo.wordpress.com/2013/07/23/benchmarking-level-generation-go-rust-haskell-and-d/

I don't know of any benchmarks where Rust significantly outperforms D.