Comment by rurban
3 years ago
Unfortunately that's needed nowadays to succeed. Java, Rust and many other would not be successful without standing on the shoulders of its big lies
3 years ago
Unfortunately that's needed nowadays to succeed. Java, Rust and many other would not be successful without standing on the shoulders of its big lies
What lies did the Rust developers make?
(Also, "nowadays" must stretch out to many decades if you're including Java!)
The three securities they guarantee and cannot hold.
Fearless concurrency.
Java also promised memory safety. I still get Null pointer segfaults in Java code.
> The three securities they guarantee and cannot hold. Could you elaborate?
> null pointer segfaults They are not segfaults and are not related to memory safety. Segfault stands for "segmentation fault", not "runtime exception". https://en.m.wikipedia.org/wiki/Segmentation_fault
If you know of a case where rust code violates memory safety without the use of an unsafe block, file a bug and it will probably be fixed within a release or two.
"Fearless concurrency" is more subjective, but rust code (again with the caveat that there isn't unsafe code, or unsafe cose upholds all unvariants) dows eliminate certain classes of concurrency bugs. Although, dreadlocks are definitely possible, and certain kinds of race conditions could potentially exist. But I don't know of any claims that concurrency bugs are impossible in rust.
8 replies →
You most likely get NPEs, not segfaults. I have never seen a segfault in Java and the first Java version I used was 1.5.
The marketing sentence "A language empowering everyone to build reliable and efficient software." is not true.