Rust the C replacement

http://esr.ibiblio.org/?p=7294&cpage=1
In practice, I found Rust painful to the point of unusability. The learning curve was far worse than I expected; it took me those four days of struggling with inadequate documentation to write 67 lines of wrapper code for the server.

Even things that should be dirt-simple, like string concatenation, are unreasonably difficult. The language demands a huge amount of fussy, obscure ritual before you can get anything done.

The contrast with Go is extreme. By four days in of exploring Go I had mastered most of the language, had a working program and tests, and was adding features to taste.

>>21
This smells like a dead striped Polecat /kebabs/, not like a cat.

I also remember that the echo implementation of GNU as well as the original echo for unix both could handle out of memory situations unlike the plan9 echo that needed to allocate a whole buffer and crashed otherwise.

>>28

the original echo for unix both could handle out of memory situations

What's the point of handling OOM if your program's only job is to send the input to stdout? What is it going to do, keep running? Might as well crash.

Of course if plan9 is doing something insane like buffering the entire input, then yeah they're idiots.

>>29
Why should it crash when it doesn't have to? Sure, running unbuffered will be slow as balls, but for forensic sys admin slow is better than nothing.