Originally posted by cl333r
View Post
Announcement
Collapse
No announcement yet.
Rust-Written Redox OS 0.8 Released With i686 Support, Audio & Multi-Display Working
Collapse
X
-
Originally posted by xfcemint View Post
(I won't even take a look at the benchmark)
Since times immemorial, there has been a tradeoff of memory usage vs. speed. Perhaps, on one nice sunny day, a "slider" will be added to compiler options so that the tradeoff can be precisely adjusted, but until that sunny day arrives, there are going to be some discrepancies in benchmarks caused by our inability to precisely set the tradeoff.
Comment
-
Originally posted by Waethorn View Post
The better OS's are always the ones that never got finished. Plan9, CP/M, Longhorn....
Ditto for IA-64.
Comment
-
Originally posted by cl333r View PostDid you notice that when Rust wins it still (almost) always uses more memory than C? (mem=>memory, right?)
- Likes 2
Comment
-
-
Originally posted by marios View PostLooks like the 0 cost safety, rustafarians are so proud of, are costlier than advertised...
- Likes 5
Comment
-
Originally posted by cl333r View PostDid you notice that when Rust wins it still (almost) always uses more memory than C? (mem=>memory, right?)
That is not necessarily true. In many of the benchmarks Rust is equivalent to C, and sometimes even uses less memory and CPU. Keep in mind that memory consumption has more to do with the algorithms used than the language itself. Rust's memory safety does not play any role in the amount of memory used.
Also, the kind of code submitted to a competitive benchmark competition is very different from the kind of code in a practical real world project. There's a lot of real world scenarios where it's easy to write an efficient algorithm in Rust that would otherwise be too dangerous to attempt in C while still having some resemblance of reliability. It also really helps out a lot that Rust's de facto string type is UTF-8 rather than null-terminated, which makes iterating and splitting possible without reallocations.
Comment
-
Originally posted by xfcemint View PostI'm not an expert in Rust, nor have I claimed that. I'm just making some high-level observations.
Either way, you are comming out as quite rude.
Originally posted by xfcemint View PostIf the benchmark allows different algorithms (i.e. algorithms have not been intentionally made the same), then it's an apples to oranges comparison.
If anyone here was making an assumption of a direct comparison, he is incorrect. Whithout taking int account differences in algorithms, any comparisons are irrelevant.
But what if a language enables you to use better algorithms that would have been to toublesome in other languages?Last edited by Anux; 25 November 2022, 09:47 AM.
- Likes 1
Comment
Comment