TWiR quote of the week

Rust enables belligerent refactoring – making dramatic changes and then working with the compiler to bring the project back to a working state.

So true : https://blog.knoldus.com/some-extensive-projects-working-with-rust/

14 Likes

Can this be the quote of the week, or do we run into weird copyright stuff?

13 Likes

xkcd is under Creative Commons Attribution-NonCommercial 2.5, so I assume the question would be whether TWIR wants to incorporate NC-licensed content.

By @alice

16 Likes

Rust was built by a secret society of Haskell developers to teach programmers how to use monads.

From https://www.reddit.com/r/rust/comments/gvjccd/why_f_rust_and_others_use_option_type_instead_of/fsqgx48/

6 Likes

We could absolutely link to it, and we could quote the text (since it's not like any of the other quotes are licensed under an Open Source license), but I don't think we could embed the image without license issues.

I'd propose linking it separately, and not making it the quote of the week.

3 Likes

"I have to say contributing to Rust way less scary than I expected with all the people answering questions"

7 Likes

This forum is licensed under the CC-BY-NC-SA.

3 Likes

From a conversation started by a new user learning Rust for the first time.

5 Likes

I appreciate this summary of Rust's (de facto) ideology:

2 Likes

About heap allocation.

6 Likes

β€˜My biggest compliment to Rust is that it’s boring, and this is an amazing compliment.’

4 Likes

On Why the developers who use Rust love it so much:

"It feels like being part of a village that learns to love the dragon it battles."

-- turbinerneiter on Hacker News

7 Likes

Perhaps one solution would be to quote that alt-text and just have a link to the image?

Pretty long quote from u/0xdeadf001short version:

The borrow checker is like the Shaolin kung fu master [...]

Long version:

4 Likes
6 Likes

Rust's beauty lies in the countless decisions made by the development community that constantly make you feel like you can have ten cakes and eat all of them too.

-- Jake McGinty et al on the tonari blog

7 Likes

References are a sharp tool and there are roughly three different approaches to sharp tools.

  1. Don't give programmers sharp tools. They may make mistakes and cut their fingers off. This is the Java/Python/Perl/Ruby/PHP... approach.
  2. Give programmers all the sharp tools they want. They are professionals and if they cut their fingers off it's their own fault. This is the C/C++ approach.
  3. Give programmers sharp tools, but put guards on them so they can't accidentally cut their fingers off. This is Rust's approach.

Lifetime annotations are a safety guard on references. Rust's references have no sychronization and no reference counting -- that's what makes them sharp. References in category-1 languages (which typically do have synchronization and reference counting) are "blunted": they're not really quite as effective as category-2 and -3 references, but they don't cut you, and they still work; they might just slow you down a bit.

So, frankly, I like lifetime annotations because they prevent me from cutting my fingers off.

-- @trentj When do you find lifetime annotations helpful?

6 Likes

Rust is like a futuristic laser gun with an almost AI-like foot detector that turns the safety on when it recognises your foot

-- goofbe https://www.reddit.com/r/rust/comments/hiyfhq/linus_torvalds_the_kernel_team_is_looking_at/fwk12r6/

6 Likes

Ownership in Rust is entirely a type system fiction.

-- @RalfJung [Brainstorming] Is there a body of research on ownership equivalent to Stacked Borrows