TWiR quote of the week

I choked on this :rofl:

24 Likes

they should just rename unsafe to C so people can shut up

u/thisismyfavoritename on Linux Kernel Rust Code Sees Its First CVE Vulnerability - Reddit

9 Likes

That'll have the expectation that you can write C code there :sweat_smile:

1 Like

Hey, what a really cool idea!

1 Like

Given C++'s origin as a superset of earlier C revisions, would cpp — C interface for Rust // Lib.rs be sufficient?

1 Like

what even is time?!?

Ralf Jung on his blog

1 Like

Great to see how Miri is progressing.

I find it amazing that by using Rust and Miri I am using tools that are on the edge of fundamental research in Programming Languages. Actual practically usable tools that anyone can use, not arcane code experiments passed around between academics.

3 Likes

Nominating ^^^

11 Likes

Feed | LinkedIn

I have written in dozens of computer languages, including specialized ones that were internal to Pixar (including one I designed). I spent decades writing C and C++. I wrote bit-slice microcode, coded for SIMD before many folks outside of Pixar had it.

I wrote the first malloc debugger that would stop your debugger at the source code line that was the problem. Unix workstation manufacturers had to do an unexpected release when this revealed all of the problems in their C libraries.

I am a better programmer in Rust for anything low-level or high-performance. It just keeps me from making an entire class of mistakes that were too easy to make in any language without garbage-collection.

Over the long term, anything that improves quality is going to win. There is a lot of belly-aching by folks who are too in love with what they've been using for decades, but it is mostly substance-free. Like people realizing that code marked "unsafe" is, surprise, unsafe. And that unsafe can be abused.

- Bruce Perens on LinkedIn

11 Likes

Great quote to use in debates with C++ cultists, when technical arguments aka facts are not enough. Though some men you just can't reach.

I might suspect that if you are lumping all statically-typed languages into a single bucket without making particular distinction among them, then you might not have fully internalized the implications of union (aka Rust enum aka sum) typed data structures combined with exhaustive pattern matching.

I like to call it getting "union-pilled" and it's really hard to accept otherwise statically-typed languages once you become familiar.

-- arwhatever

3 Likes

Quote by @khimru in this thread.

It isn't specifically Rust related, but it made me chuckle, so I decided to nominate this quote.

2 Likes