> Memory management is difficult, extremely difficult, to get correct in the way rust does
Memory management isn't hard --- you just need to pay attention to detail and not say "YOLO, let's abort on OOM" like the Rust stdlib does. Rust is an unacceptable language for anyone who cares about robustly responding to heap exhaustion.
Re:Crystal: Fast as C, Slick as Ruby
by Turing_Machine on Thursday August 04, 2016 @09:40PM
(#12229589)
"Memory management isn't hard --- you just need to pay attention to detail"
You're quite right. The problem is that every bit of attention you spend on that detail is attention that you're not spending on details that are actually solving your problem.
I programmed in C for decades. I do not miss malloc() and free() in the least.
(I still do use C when the situation warrants, but the situations where it is warranted are becoming rarer and rarer with each passing year).
> If you don't have latency, memory restrictions, or embedding requirements
Add power consumption to that list.
I think you meant
-> 'extreymely difficult to get INcorrect in the way rust does'
Unless this is a joke, its meaning is correct, i.e. "proven correct like Rust".
GC isn't terrible, though. Azul has struck an amazing balance between latency and eagerness—even if you can't afford it the technology does exist. If you don't have latency, memory restrictions, or embedding requirements, rust may be overkill.