TWiR quote of the week

Why do I use the letter ‘o’ for my generic closure param name? [...] I recently realized that since Rust uses pipes to enclose a param block, using ‘o’ makes the block look like a TIE fighter. I am not a terribly serious person.

-- @MrTact, Polishing Rust


Rust is Fast, Mutable ML with a compiler that gives you grief.

@sycration on Discord

(The rest of the quote is really good too, go read it :stuck_out_tongue: )

1 Like

Describing Rust as a systems programming language in 2021 is like describing Microsoft as Windows or Google as search. Yes, Rust is equipped for systems programming, but its applicability is much wider.

Tim McNamara on Twitter


Rust is so easy even neurosurgeons can understand it

/u/baseball2020 on reddit


I'm starting to think of the compiler and borrow checker as training wheels for writing correct code, which I'm trying to end up relying on less and less. While they can definitely feel like a wall, you just have to find the doors.

@PFaas in Rust is too hard to learn


What I have been learning ... was not Rust in particular, but how to write sound software in general, and that in my opinion is the largest asset that the rust community tough me, through the language and tools that you developed.

Under this prism, it was really easy for me to justify the step learning curve that Rust offers: I wanted to learn how to write sound software, writing sound software is really hard , and the Rust compiler is a really good teacher.


This ability to identify unsound code transcends Rust's language, and in my opinion is heavily under-represented in most cost-benefit analysis over learning Rust or not.

@jorgecarleitao, Thank you for the teaching on how to write sound software


Having a fast language is not enough (ASM), and having a language with strong type guarantees neither (Haskell), and having a language with ease of use and portability also neither (Python/Java). Combine all of them together, and you get the best of all these worlds.

Rust is not the best option for any coding philosophy, it’s the option that is currently the best at combining all these philosophies.

/u/CalligrapherMinute77 on reddit


Perhaps this is an oblique reference to RESF?

1 Like

"Stream is an Iterator, but instead of advancing space you're advancing time."

Esteban Kuber on twitter


The main theme of Rust is not systems programming, speed, or memory safety - it's moving runtime problems to compile time. Everything else is incidental. This is an invaluable quality of any language, and is something Rust greatly excels at.

( over 18? in Advantages of building a CRUD web application in Rust? : rust)


Little lengthy, but quite accurate.

Have you seen someone juggle several items with one hand? That's the point of async. Blocking (non-async) it like writing - it requires constant work from each hand. If you want to write twice as fast you'll need two hands and write with both at the same time. That's multithreading. If you juggle, the moment the item leaves your hand and is in the air, you have it left with nothing to do. That's similar to network IO - you make a request and are just waiting for the server to respond. You could be doing something in the meantime, like catching another item and throwing it back up again. That's what "await" does - it says I threw and item into the air, so I want my current thread / hand to switch over to catch something else now.

Source from the same user as last week!


don't worry: in 20 years we won't have Rust 2.0, but some upstart kid is gonna take all the lessons and mistakes we learned by then, make the Grime language, and slowly put us all out of work. Then we truly will be C++.

I can't wait for this day!

@Lokathor and @nikomatsakis on Zulip (archive)


Finally, I feel it is necessary to debunk the “ fighting the borrow checker ” legend, a story depicting the Rust compiler as a boogeyman: in my experience, it happens mostly to beginners and the 1% trying to micro-optimize code or push the boundaries. Most experienced Rust developers know exactly how to model their code in a way that no time is wasted fighting the compiler on design issues, and can spot anti-patterns at a glance, just like most people know how to drive their car on the correct side of the road to avoid accidents, and notice those who don’t!



I remember reading something from a coder who grew up on C, learned Rust, and the next time he had to write something in C, got really frustrated with all the bugs the compiler let through, since he then knew that it was possible to catch them at compile time.

That stuck with me and changed how I think about my fights with the borrow checker a bit.

/u/antichain @ Reddit - Dive into anything


We describe a lot of things as “how systems work” when really it’s “how C works” and part of Rust’s integration pains are just that it’s the first thing to credibly come into spaces and not fit in a C-shaped hole.


It's a great example of the different attitudes of C/C++ and Rust: In C/C++ something is correct when someone can use it correctly, but in Rust something is correct when someone can't use it incorrectly.


I think Rust is in an interesting place wrt specs because it straddles two kinds of language communities -- C/C++/JS, with serious specs and multiple implementations, and Ruby/Python/Go, with reference manual, a test suite, and a single canonical implementation.
Rust is a place where both of those traditions are being forced to reckon with the reasons why the other tradition exists.

Sam Tobin-Hochstadt on twitter


C binaries are smaller than rust, cars are lighter without seatbelts

-- Radomane in togglebit's chat


That's misleading, as Rust's safety has nothing to do with why the binaries are larger.


C binaries are smaller than rust, cars are lighter without seatbelts

I doubt that either of those statements is true.

Rust binaries can be really small. See what Cliff Biffle does:
On tiny micro-controllers: Rewriting m4vgalib in Rust - Cliffle
On web assembly: Making really tiny WebAssembly graphics demos - Cliffle

I'm pretty sure that many modern cars with seat belts are lighter than old cars without.
The "seatbelts" of the Rust language do not necessarily require adding code to the binary. Mostly not.

Besides, car analogies are always terrible. And the number of instructions required to do anything are not a function of the source language per se.