TWiR quote of the week

But it's not failure to uphold "ownership" that causes a crash. It's use-after-free, double-free, or even logic errors. Ownership is a technique (enforced by Rust's borrow checker) that ensures you meet the dynamic requirements of the system, not the requirement in and of itself. It's in that way that ownership is a "fiction;" the actual dynamic model of the code has no care about whether you follow the ownership "pattern" or not, just that you meet these more simple requirements.

But we've derailed this thread more than enough already :slight_smile:

1 Like

Topic: "Linux Developers May Discuss Allowing Rust Code Within The Kernel" by Almindor

I definitely wouldn't use Rust for some tasks but embedded, systems/kernel programming, drivers and some back-end stuff is where I think it brings SO much to the table it'd be crime not to use it.

Source: https://www.phoronix.com/forums/forum/software/programming-compilers/1192467-linux-developers-may-discuss-allowing-rust-code-within-the-kernel?p=1193367#post1193367

I don't think we should be linking to the Phoronix comments section, no matter what someone says there. :slight_smile:

4 Likes

From Why choose rust over C or C++:

7 Likes

Humor by @FedericoStra in response to

14 Likes

unsafe Rust is all about flirting with UB but never giving in.

@RalfJung on zulip

13 Likes

Once you realize that the Rust borrow checker is actually preventing you from writing bug after bug, you start to wonder how we ever got this far without it.

10 Likes

Empowering is the perfect word to describe Rust in 2020. What used to be a rough adventure with many pitfalls has turned into something beautiful, something that can lift your spirit. At least, that’s what it did for me.
Mathias Lafeldt in https://sharpend.io/giving-rust-another-shot-in-2020/

9 Likes

source

8 Likes

If you've never tried Rust, imagine pair programming alongside a nearly-omniscient but narrowly-focused perfectionist.

Source

20 Likes
14 Likes
14 Likes

I'll admit, I've sat at my desk with a huge smile thinking "I couldn't have built this without lifetimes."

Via /u/Theemuts in /r/rust

5 Likes

The amount of careful thought I've seen put into [Rust's] design – crafting async/await to work in no_std environments, or the new inline assembly syntax – has produced a language that is not only better than what I could have designed, it's better among axes I was not even aware existed prior to reading the Rust RFCs.
-- https://john-millikin.com/first-impressions-of-rust

15 Likes

This is not a commentary on the actual issue that triggered this response. Rather, I just liked the response.

9 Likes

Whoop whoop, this feels like being knighted, and all the work totally paid off. Iteration after iteration after iteration, and it really was just Rust pushing me into doing "what's right", which also happens to be fast as a freebie.

-- Sebastian Thiel in https://github.com/Byron/gitoxide/issues/1#issuecomment-672636220

1 Like

There is a more technical term for "wrong", too - maintaining invariants is maintaining "soundness". Code that breaks invariants is called "unsound".

-- https://fasterthanli.me/articles/frustrated-its-not-you-its-rust

You're smarter than Rust - and you may need to rethink your design a bit, so it's possible to tell the compiler about it.

And when you do, you'll discover mistakes you never knew you could make.

-- https://www.reddit.com/r/rust/comments/i9sor7/frustrated_its_not_you_its_rust/g1h6a7a/

6 Likes

“macros are for when you run out of language”. If you still have language left—and Rust gives you a lot of language—use the language first.

-- https://twitter.com/pcwalton/status/1294676975575896064

12 Likes

Not only is our new Rust code simpler and cross-platform, but it’s faster to boot!

~ https://astropad.com/why-rust/

1 Like