TWiR quote of the week

[parasyte]

@daboross

I think that python and rust often also share some of the same problems where idiomatic code is easy to read, but hard to write. It can be very difficult to figure out the "right" way to do things in either language as a beginner.

I'd like to include the whole quote, but it's two paragraphs. This is the best takeaway, IMHO.

[tesuji]

From Did Rust make the right choice about error handling? - #29 by ZiCog

@ZiCog

The whole motivation behind exceptions is to allow one to write ones business logic, concentrate on what one likes to think ones program will do, without having lots of fiddly error checking and handling code obscuring that logic. Error situations are therefore swept under the carpet with "try" and kept out of sight with "catch".

However in my world view failure is not exceptional, it is a common happening, it's too important to be hidden away. Therefor failure handling should be in ones face in the code you write. Certainly in the face of those that read it.

[H2CO3]

But then again, what isn't hard as a beginner?

[TomP]

@kornel

because impl Trait wants one type only, and every future is a unique snowflake.

Brilliant characterization by analogy!

[L0uisc]

Memoize function without cloning - #2 by red75prime
Most functional languages use garbage collection, so memory management is not a concern there. In Rust we need to do something explicitly.

Explaining why the borrow checker is complaining and how to deal with it.

[trentj]

@kornel

Things that are programming patterns in C are types in Rust.

A concise description of what I find compelling about Rust's approach to correctness.

[tshepang]

One problem I've had, in general and not with just Rust, is that people can find a way to do anything with anything. I've seen people do some horrific stuff with their hammers just to prove they don't need a screwdriver.

seen on /r/rust

[ssokolow]

[SIMD is] the perfect knife edge between awe and expletives.

-- Stephen Merity @ Smerity.com: An introduction to SIMD and ISPC in Rust

[alanhkarp]

That's the way I feel about the borrow checker.

[dunnock]

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/

[mark-i-m]

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

Carcinization

[ssokolow]

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

[RustyYato]

@alice

You don't declare lifetimes. Lifetimes come from the shape of your code, so to change what the lifetimes are, you must change the shape of the code.

By @alice

[jyn514]

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/

[josh]

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.

[josh]

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

Chat for distributed teams

[notriddle]

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

[parasyte]

@duli

The concept of ownership is really strong and Rust made me see things from a different perspective. It is also elegant. The borrow / move terminology is much more appealing for beginners like me.

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

[BatmanAoD]

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

@tuxmain

The aim of developing Rust is to make the world closer to a certain ideal world. This ideal world is an ideology, and some people could find it is not ideal. This ideal world seems to have these properties:

• people do not fear bugs or panics while using a computer;
• computers are more useful because programs are faster and lighter;
• things are interoperable;
• developers can use free software;
• etc.

[amos]

@H2CO3

Heap allocation might be expensive, but sometimes it is necessary.

Houses are expensive too, but I wouldn't call anyone naive for buying a house.

About heap allocation.