News for hackers. Stuff that matters.
Re:A Little Story About the `yes` Unix Command by Annatar on Thursday October 12, 2017 @07:11AM (#15457120)
But what if one doesn’t care about memory safety because one has other languages at one’s disposal, like shell, AWK, Lisp? What benefit does Rust bring then? And at what price?

And who is to say that the programmers of Rust built a perfect language that always generates code which is bounds-safe? I question that as I know from experience that no human has ever written 100% correct code 100% of the time; even machines aren’t capable of achieving that. Therefore, I hold that the entire promise of Rust is flawed. I don’t like Rust one bit.

Re:A Little Story About the `yes` Unix Command by steveklabnik on Thursday October 12, 2017 @08:34AM (#15457489)
We had a large community discussion about this last year: https://brson.github.io/fireflowers/
Re:A Little Story About the `yes` Unix Command by cat199 on Thursday October 12, 2017 @09:26AM (#15457756)
I don't think that theme is bright enough.

Perhaps neon green with yellow letters would do the trick?

Re:A Little Story About the `yes` Unix Command by rurban on Saturday October 14, 2017 @05:19AM (#15471432)
Problem is that Rust is not memory safe anymore, since they switched from GC to refcounting and added unsafe. Pair that with being no concurrency safety (deadlocks, races) there are only macros left which do make rust attractive.

On the other side there are proper languages which do provide all safeties and beat rust or C++ in performance, such as pony. A proper type-system does help (compile-time guaranteed), but you could also add such features to the run-time system (e.g. a GC or safe threading with a single-writer system such as parrot). With rust you don't have any of it, you have to manually add locks or mutexes into your threaded code, and try to avoid unsafe.