TWiR quote of the week

There are no emoji for higher-order-camels, so please don’t ask about that case :wink:

— shepmaster, https://github.com/rust-lang/rfcs/pull/2389#issuecomment-378753609

7 Likes

A bit sharp, but nevertheless funny:

Haskell/Idris folks is probably the last group of users I’d personally care about, they have every piece of punctuation occupied for something highly useless for non-PL-enthusiasts.

petrochenkov on internals

7 Likes

Holy ****! This compiler is like my dad, won’t let me do anything wrong!!

@cg-cnu’s wife expressing rust’s safety morals, in isn’t rust too hard to be adopted (censored by me, just in case)

7 Likes

Rust is one of those friends that take some time to get along with, but that you’ll finally want to engage with for a long term relationship.

From this blog post about Go

12 Likes

I’ve become fearless in Rust, but it’s made me fear every other language…

u/bluejekyll on reddit

27 Likes

last time i talked to the infra team they made a bot to replace kennytm. i fear if I ask them to write a rust based unikernel with a custom os to host the docs they’ll actually do it

@killercup on Twitter

16 Likes

Explicitness is the fourth core value of Rust. Ironically, I don’t see that “Explicitness” is ever explicitly stated as a goal of Rust. But, given the choice between implicitness and explicitness, Rust usually chooses explicitness.

iwhitney in Rust via its Core Values

More of a tongue twister, but its true! :smile:

8 Likes

“Rust is difficult because writing correct code is difficult” – @leodasvacas

Said about this post: Isn't rust too difficult to be widely adopted?

Originally in Portuguese: https://t.me/rustlangbr/65133

14 Likes

:crab:

1 Like

Software is partly a production problem, but it’s mainly a maintenance problem. Powerful primitives like Rust are our path to building sustainable services that don’t need human attention around the clock, and which can be expected to operate reliably over epochs measured in decades instead of weeks.

https://brandur.org/fragments/rust-reflections

12 Likes

Well I didn’t expect the bloody Rust Evangelism Strike Force.

bursts through conveniently placed door

NOBODY EXPECTS THE RUST EVANGELISM STRIKE FORCE! Our chief feature is safety. Safety and speed. Our two main features are safety and speed. And fearless concurrency. Three! Our three main features are safety, speed, and fearless concurrency. And a fanatical devotion to Ferris.

– /u/shadow31 on Reddit at https://www.reddit.com/r/rust/comments/8ga2tt/rust_game_lag/dya0beb/

16 Likes

See also the post above, posted closer to when that Reddit copypasta was originally generated: TWiR quote of the week

1 Like

you should donate your brain to science once the time comes…
– freakhill, in response to dtolnay’s reflect library

2 Likes

(has niko become rustc’s dad?)

eddyb

1 Like

“We’re able to replicate the structure of cows, but not their lifetimes, in C++, which makes Cows dangerous.” – https://twitter.com/hsivonen, closing his talk about integrating Rust and C++

13 Likes

Excellent showcase of the potential of multithreading, unlocked by Rust:

TL;DR: I reduced the dump time from 506s to 26s by fixing some simple issues and taking advantage of Rust “fearless parallelism”.

From: Speeding Up dwarfdump With Rust

4 Likes

When picking up a lentil (Result) a pigeon (?) must consider two options. If the lentil is a good one (Ok), the pigeon simply puts it into the pot (evaluates to the wrapped value). However, if the lentil happens to be a bad one (Err), the pigeon eats it, digests it (from) and finally “returns” it. Also the silhouette of a pigeon kind of resembles a questionmark.

From @anatol1234 on internals.

2 Likes

(after explaining bit of Rust using Java)

I’m sorry to have subjected you to Java. You can stop weeping and screaming now, you’re not in the first year of your computer science course anymore. Unless you are, in which case I’m so sorry.

http://troubles.md/posts/why-phantomdata/

3 Likes

It can seem overwhelming when starting to learn Rust, because some of the stuff you need to be productive is more complex than in C++ (e.g. the borrow checker) so the initial curve from zero to productive is steeper, but it soon becomes second nature and then it’s smooth sailing. Whereas in C++ it’s easier to get started but you’ll be sailing in a stormy sea with monsters (who want to segfault you) from the start, and have to spend a lot of time debugging…

@Boscop on reddit https://www.reddit.com/r/rust/comments/8qkv6a/im_worried_were_going_to_reach_c_levels_of/e0kel9x/

13 Likes

(Update: It’s from https://github.com/rust-lang/rfcs/pull/2457#issuecomment-396811743)

2 Likes