Eric S Raymond, author of "The Cathedral and the Bazaar", blogs via Ibiblio
I wanted to like Rust. I really did. I've been investigating it for months, from the outside, as a C replacement with stronger correctness guarantees that we could use for NTPsec [a hardened implementation of Network Time Protocol].
[...] I was evaluating it in contrast with Go, which I learned in order to evaluate as a C replacement a couple of weeks back.
[...] 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 [a simple IRC] 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.
Have you tried using Rust, Go or any other language that might replace C in the future? What are your experiences?
(Score: 2, Funny) by Runaway1956 on Monday January 16 2017, @09:17PM
Wow, you finally got something right. Runaway can't code. On a good day, Runaway can step through some other person's code, and see what's happening. But, Runaway just never got into coding. The most complicated thing he has ever done was to code a game on a TRS-80, way back in the day when BASIC was a thing. I even saved it to cassette, so that I could play the game again, and again.
But, none of that has anything to do with my reply to AC above.