TWiR quote of the week

[zeroexcuses]

@sanxiyn

This is safer than you may think, because those who need async tend to know it themselves and don't ask "should I use async" question. In other words, asking itself is a signal that answer is no. MITM proxy case was a rare exception.

(On maybe not using async).

[Julian-Wollersberger]

Important crab-related diagnostics improvement shipping in nightly
@rustlang
1.59:

error: Ferris cannot be used as an identifier
 --> src/main.rs:2:9
  |
2 |     let 🦀 = 123;
  |         ^^ help: try using their name instead: `ferris`
3 |
4 |     for i in 0..🦀 {
  |

https://twitter.com/m_ou_se/status/1471077145258647554

[andresovela]

@matklad

Another interesting alternative is to have a low-level language which is OK for high-level stuff. And here I think Rust is very unfairly fortunate.

@matklad in Rust will revolutionize ecosystem of high level language?

[robin]

So I think this is what many Rust developers means when they say zero trust cost abstractions.

Rainer Stropek in Traits, not your grandparents' interfaces.

Please do not publish this one, (EDIT2: I don't think it's worth publishing) I just fond the slip of the tongue very funny!

EDIT: this post has been flagged as off-topic. I would have like to know why. This is a citation, about Rust, from a very interesting conference, and I selected it because it was funny. And while I think its not worth publishing it in TWIR because it doesn’t bring any new insight about Rust, I think it has its place in this thread for the pleasure of people that propose and vote for TWIR citations.

[notriddle]

This thread is for submitting Quotes of the Week for This Week in Rust. If you don’t want your quote to be published, then it probably doesn’t belong here (though TWiR quotes that are just funny have been published before).

[jhpratt]

By no means a "learning" kind of quote, but…

I just discovered an absolutely critical bug in the Rust logo:

It's not symmetrical! The inner and outer circle of the gear don't even have the same center.

from Mara Bos here

(yes, this has somehow gone years without anyone noticing)

[Cyborus]

@jhpratt

By no means a "learning" kind of quote, but…

Oh come on, I was just about to go to sleep...

[josh]

Self-nomination:

One reason we keep certain things as hard errors rather than lints: it establishes a baseline that you can safely assume about other people's code, since it can't be turned off. And as a result, that baseline can become part of people's mental model of Rust itself, rather than something that might or might not be true in any given codebase.

We have to take care to not use that lightly, because that places work on all users of Rust to maintain code to that baseline. But there are cases where we do. We don't allow using one integer type where another was expected. We don't allow certain operations outside an unsafe block. ...

I think the standard we should apply is asking whether something is part of the baseline that people should be able to assume about all Rust code, and if that's worth the tradeoff of requiring that baseline of all Rust users.

Lack of `mut` in bindings as a deny-by-default lint

(The elision there is to avoid making any commentary on the actual issue in that topic part of the quote; in general, I think we should avoid highlighting quotes that directly comment on one side of an active topic, so I left that part out.)

[robin]

I’m saddened to think that because this industry has an obsession with making programming accessible to the lowest common denominator, expressive and innovative languages like Rust will fall by the wayside, and we’ll all be writing code in languages like Go and Python in the future because they’re “easy” and even high schoolers can learn them in a couple days.

By booleandilemma on hacker news

[Michael-F-Bryan]

@H2CO3

Don't try to squeeze all of this into a "one-liner". Brevity is not in itself a virtue.

A nice reminder that sometimes the shortest answer isn't the best one.

[ssokolow]

Fun fact if you repeat "Thread scoped private field injection" 3 times to a Mirror you will summon a demon.

-- MyLifeAsSinusOfX @ Reddit - Dive into anything

[Yandros]

For any language SomeLang™:

@codespear

It is very likely that my C++ [SomeLang™] code will be faster if I rewrite it in C++ [SomeLang™].

The context of that thread is already interesting on its own, but I even think that taking that quote seriously / in a first degree fashion is actually meaningful: for some codebases written from scratch and which developed features out of an initially thin core, the newly obtained perspective on the problem ought to make rewriting that codebase "from scratch" yield cleaner, leaner, and potentially faster code (and back to that RiiR thread, hence why sometimes the Ri part may be just as important if not more important than the iR part).

[llogiq]

Self-suggestion:

The error message code will at one point become sentient and decide to send a robot back in time to save mankind from skynet [...]

(Rust 2021 – Looking Back and Forth — Llogiq on stuff)

[josh]

I performed an extremely scientific poll on twitter, and determined this is not how it's pronounced

Well, it really is Vec<T, A>, pronounced Veck-tah.

Look, I moved away from Boston to avoid this sort of thing .

-- thomcc and the8472 in Remove pronunciation guide from Vec<T>

[moises-marquez]

"For me, the joy of Rust comes from the fact that I can write code that represents the mental model I have of the problem" - Jon Gjengset, 2022-01-01 Q&A/AMA/Whatchamacallit.

I resonated so strong with this statement. This is the reason why I find joy in Rust and I evangelize about it.

[woshilapin]

I see a lot of “we rewrote X in Rust and it got faster” posts. I think that if you rewrite anything from scratch with performance in mind, you’ll see a significant performance improvement. I’m suspicious of how much Rust itself is needed versus the developers having some performance discipline.

By Chris Done on My negative views on Rust.

[ssokolow]

So why aren't we all fuzzing security-sensitive surfaces, at least for a modest number of cycles? Well that comes down to the difference between apes and programmers: apes know when they should be using tools.

-- Tiemoko Ballo @ Tiemoko Ballo

[KillTheMule]

is turbofishing a verb?

jbe @ Replace type annotation with turbofish - #2 by jbe

[amos]

@ZiCog

I have just been reading that data centres in Ireland are consuming about 10% of the nations electricity generation capacity and the Irish power grid is under strain.

Scale that thought up around the world and we see that is a huge amount of power consumption. No doubt resulting in a huge amount of C02 emissions and hence global warming.

Given that programs written in PHP, Javascript, Python, Java etc are so inefficient, using more CPU cycles and hence energy, I conclude it is a moral imperative not to use them on such scale.

So, use Rust. Efficient and safe.

@ZiCog on Negative views on Rust ( not mine! )

[CAD97]

Over on IRLO,

@skysch

Language stability is not just about semver compatibility. It's also about not burdening developers to have to make new decisions when looking at old code. [Language instability] creates churn and debate about things that previously didn't require it.