3 ms·

"we truly don't believe we could have achieved these numbers with this level of stability without Rust" Oh please. This is just rust sensationalism. People don

"we truly don't believe we could have achieved these numbers with this level of stability without Rust" Oh please. This is just rust sensationalism. People don't truly believe rust is faster than C do they?

bufferoverflow 6y ago
In some problems Rust is the fastest: https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/nbody.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/spectralnorm.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/revcomp.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/binarytrees.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
- jonny383 6y ago
  Every single one of those rust implementations is using unsafe {}, thus defeating the purpose of using rust in the first place. Run the same benchmark without unsafe {}.
  - turndown 6y ago
    >defeating the purpose of using rust in the first place I don't think this is true; the whole point of Rust is that unsafe operations are explicit, not that you never do so. Also, I looked at the first one, and it's only using unsafe on what are basically op code calls; I don't think it is realistic to complain about that.
  - igouy 6y ago
    Not true. Of those 4 tasks, the rust programs for task 3 and task 4 do not use the keyword "unsafe". For task 2, the spectral-norm Rust #6 program does use "unsafe" but #5 does not and it's almost as fast.
gpm 6y ago
Developing stable complex software in C takes a hell of a lot more effort and skill than it does in Rust IMO.
bschwindHN 6y ago
I don't believe Rust is faster than C, but I would argue it's faster to develop new products in Rust vs. C, and easier to produce programs which don't have data races or invalid memory accesses.
- jonny383 6y ago
  Sure, if you wrap everything in unsafe and/or import third party libraries (with the assumption they are also safe).

bufferoverflow 6y ago

In some problems Rust is the fastest: https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/nbody.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/spectralnorm.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/revcomp.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/binarytrees.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

jonny383 6y ago
Every single one of those rust implementations is using unsafe {}, thus defeating the purpose of using rust in the first place. Run the same benchmark without unsafe {}.
- turndown 6y ago
  >defeating the purpose of using rust in the first place I don't think this is true; the whole point of Rust is that unsafe operations are explicit, not that you never do so. Also, I looked at the first one, and it's only using unsafe on what are basically op code calls; I don't think it is realistic to complain about that.
- igouy 6y ago
  Not true. Of those 4 tasks, the rust programs for task 3 and task 4 do not use the keyword "unsafe". For task 2, the spectral-norm Rust #6 program does use "unsafe" but #5 does not and it's almost as fast.

gpm 6y ago

Developing stable complex software in C takes a hell of a lot more effort and skill than it does in Rust IMO.

bschwindHN 6y ago

I don't believe Rust is faster than C, but I would argue it's faster to develop new products in Rust vs. C, and easier to produce programs which don't have data races or invalid memory accesses.

jonny383 6y ago
Sure, if you wrap everything in unsafe and/or import third party libraries (with the assumption they are also safe).