The Rust compiler is basically 30 years of trying to figure out how to teach a computer how to see the things we worry about as C developers.
Sometimes a pun arises in the middle of description...
C is about simplicity at any cost. Rust is about simplicity at a pick-your-own-price.
eo5g on r/rust
I don’t like Rust being pigeon holed as a “safer C++”—it’s so much more than that.
"Rust compilation is so slow that I can fix the bugs while it still compiles the crates"
Did you say that right now or is it a quote from somewhere?
Yes, I said that but you can quote me.
-- Rustafarian three days ago in this thread
/u/reyqt: It will be fine until compiler complain [sic] about your code
@steveklabnik: "describe rust in one sentence"
Rust helped me grasp concepts I should have known when writing C++
-- Microsoft intern Alexander Clarke in this blog post: https://msrc-blog.microsoft.com/2019/10/16/an-interns-experience-with-rust/
Slightly off-topic, but I've had the experience in the exact opposite direction: having written lots of C++ and having been constantly looking for improvements and patterns that ensure safety, Rust had basically no learning curve for me.
As the intern honestly admits in that blog, most users of high level languages have no idea where the memory is they are using and who else is using it. It's not something they think about until they get the segfaults and corrupt data.
Memory in C++ is a leaky abstraction (see what I did there )
I came from C# where I found that low level memory things were kind of swept under the rug and left to the compiler to deal with. These kinds of things interested me so I tried C++. To put it simply, I was not prepared to deal with C++, so I instead switched to Rust, and have found that dealing with the details of low level things can be nice and refreshing little niches, opposite to my experience in C++ and present compared to C# (At least at the time and my understanding of it).
let txt = child.expect("this is safe") .get_text().expect("this is safe");
…man, starting to dig through the source code of a really large open source program is so weird. It’s like wandering around a giant cathedral that’s being constantly renovated and repaired and maintained over the course of years by a giant team of invisible crafters and architects, who mostly communicate via notes and designs pinned to the walls in various places.
Woah, I just came here to suggests this. I'm only half surprised someone else has before.
Aaaaaa I wrote an article because of a quote in TWiR and now a quote from it is being submitted to TWiR!