there are two hard problems in computer science:
- writing software that isn't in rust
- naming things
I suspect naming things should be number 1 on the list. Even Rust does not help us with that.
We've previously had QotWs that weren't specifically about Rust, haven't we? I think that's actually a good thing; QotW are quotes the community "likes", which should arguably say more about the community than about Rust the technical project.
If being directly relevant to Rust is not required my quote of the week comes from Russell Anderson in some video about some kind of programming on YouTube I found last night:
I can make software, without knowing, whatever it is that I'm doing.
Bombfuse, on the unofficial Rust discord, on the topic of scripting languages for game engines.
batisteo on Reddit
As a community, we won’t let the borrow checker be more friendly than us!
considering i learned that lesson from writing a bunch of rust code, there may be more of a connection than you think
In russian if one not sure they would say "да нет наверное" which literally translates "yes no maybe"
I both strongly agree and strongly disagree.
Telling a programmer there's already a library to do X is like telling a songwriter there's already a song about love.
-- PeteCordell #NoDealNoWay (@petecordell) January 29, 2014
Suggested by matthieum on reddit.
My friend found several copies of The Rust Programming Language in the gift shop of the International Spy Museum in Washington, DC. According to him, there were no other programming-related books, only the Rust book.
I must know how this happened. Please help me solve this important mystery.
I love this reply there:
"Well a Museum purpose is also memory safety, I guess."
In case anyone just wants to know why the gift shop has TRPL, one redditor wrote them an email and got a response:
I said it before, and I'll say it again: If one views Rust as a critique on C++, one should view it as a constructive critique.