I'd like to include the whole quote, but it's two paragraphs. This is the best takeaway, IMHO.
But then again, what isn't hard as a beginner?
Brilliant characterization by analogy!
Memoize function without cloning - #2 by red75prime
Most functional languages use garbage collection, so memory management is not a concern there. In Rust we need to do something explicitly.
Explaining why the borrow checker is complaining and how to deal with it.
A concise description of what I find compelling about Rust's approach to correctness.
One problem I've had, in general and not with just Rust, is that people can find a way to do anything with anything. I've seen people do some horrific stuff with their hammers just to prove they don't need a screwdriver.
[SIMD is] the perfect knife edge between awe and expletives.
-- Stephen Merity @ Smerity.com: An introduction to SIMD and ISPC in Rust
That's the way I feel about the borrow checker.
Rust enables belligerent refactoring – making dramatic changes and then working with the compiler to bring the project back to a working state.
So true : https://blog.knoldus.com/some-extensive-projects-working-with-rust/
Can this be the quote of the week, or do we run into weird copyright stuff?
xkcd is under Creative Commons Attribution-NonCommercial 2.5, so I assume the question would be whether TWIR wants to incorporate NC-licensed content.
Rust was built by a secret society of Haskell developers to teach programmers how to use monads.
We could absolutely link to it, and we could quote the text (since it's not like any of the other quotes are licensed under an Open Source license), but I don't think we could embed the image without license issues.
I'd propose linking it separately, and not making it the quote of the week.
"I have to say contributing to Rust way less scary than I expected with all the people answering questions"
From a conversation started by a new user learning Rust for the first time.
I appreciate this summary of Rust's (de facto) ideology:
About heap allocation.