TWiR quote of the week

Touch fish

estebank reads other people's mind, that's why he's so good at writing helpful compiler errors.


Context: in response to the Rust for Linux folks building and presenting an NVMe driver that's roughly at parity with the performance of the C driver.



Hi, I'm Matthew Wilcox, co-author of the NVMe spec and the troublemaker who said 'you need to do an NVMe driver and then I'll believe that Rust is ready for use in the kernel.' You have succeeded far beyond my expectations, both of you, all of you, thank you so much, you've done a fantastic job. I was not expecting to see these performance numbers, they are amazing.


[The] difficulty lies in an unfamiliarity with a memory model that challenges 50 years of running by the pool with scissors. There will always be a demand for programmers who know how memory works, and there will always be people who garbage collector go brrr.

— Guilty-Speaker7044 on reddit

1 Like

Does the quote need to be from this week? I find this quote by @josh very relevant in the context of recent discussion on async dyn traits, dyn impl and placement return:

To me, a defining property of Rust is that it never gives that "I'm not in control here, the language is" feeling.


Which is a very odd statement to my mind. Because Rust exercises great control over many things, thus stopping us writing code that mysteriously crashes, eats memory or produces erroneous results at random.

I think it's because the type system is "a relatable master", while the thought processes of the optimizer, when we're allowed to observe them having unexpected effects, are that of an eldritch abomination.

Speaking of languages, it's time to halt starting any new projects in C/C++ and use Rust for those scenarios where a non-GC language is required. For the sake of security and reliability. the industry should declare those languages as deprecated.

— Mark Russinovich, CTO of Microsoft Azure



it's not Perl

Linus Torvalds complimenting Rust, source: Next steps for Rust in the kernel []


Rust isn't that terrible

Also Torvalds, from the same quote as above. This is high praise indeed coming from Linus.


I would say the benefits I saw from the start were that you didn’t have to think about race conditions and memory corruption, and memory safety in general. You know, just writing correct and robust code from the start. So that was basically my first impression, but now I have also come to realize that there are many other aspects. You get just as big benefits from the side effects of that first aspect.


Semver has its philosophy, but a pragmatic approach to versioning is:

<upgrades may break API> . <downgrades may break API> . <fine either way>

Beatifully put by @kornel in this thread.


people don’t realize that the reason their idea doesn’t work is not because the idea is wrong, it’s because the language (or, often, the compiler) is limited.

By Niko Matsakis in this blog post.