I think you are missing the point. The quote is about C and C++ being superseded by Rust. It's not against any person or group, and you have to interpret in its own context, which was given by the linked thread. Rust brought new developments to systems programming that cannot be retrofitted to C and C++, and that's a pretty damn good argument in favor of it.
3 Likes
But quotes are, by definition, taken out of context. Thus, regardless of how good it is in context, it's of questionable suitability for a QOTW.
13 Likes
I learned long ago, never to wrestle with the Rust compiler. You get dirty, and besides, the compiler likes it.
9 Likes
Meanwhile the Rust shop has covers on everything and tag-out to even change settings of the multi-axis laser cutter, but you get trusted with said laser cutter on your first day, and if someone gets hurt people wonder how to make the shop safer.
8 Likes
Rust would be better if it were written in Rust.
LLVM backend
Good news!
(wasmtime/README.md at main · bytecodealliance/wasmtime · GitHub)
"Aha, but std still has a libc dependency -"
(GitHub - bytecodealliance/rustix: Safe Rust bindings to POSIX-ish APIs)
"But the syscalls are still implemented in C -"
"But what about disk controllers, and firmware, and drivers, and everything else? Surely there isn't some way to completely avoid C?"
(from reddit)
1 Like
@lina @dougall While working on these userspace Mesa changes today, I did not hit a single GPU kernel driver bug. Not. A. Single. Bug.
This is thanks to Lina's phenomenal efforts. She took a gamble writing the kernel driver in Rust, knowing it would take longer to get to the first triangle but believing it would make for a more robust driver in the end. She was right.
A few months of Lina's Rust development has produced a more stable driver than years of development in C on certain mainline Linux GPU kernel drivers.
I think... I think I have Rust envy
....Or maybe just Lina envy
6 Likes
Regarding the friction you feel when writing embedded Rust in the same way you wrote embedded C++...
9 Likes
A fun little jab and hat tip to the Rust community...
I'm expecting this article to make the rust crew go in a crusade again, and I think I might be with them this time.
http://blog.pkh.me/p/37-gcc-undefined-behaviors-are-getting-wild.html
3 Likes
On appreciating explicitness in code:
9 Likes
To date, there have been zero memory safety vulnerabilities discovered in Android’s Rust code.
15 Likes
Or maybe this one:
Safety measures make memory-unsafe languages slow
(Same source)
5 Likes
Strongly seconded, and I'd even suggest potentially highlighting the article even more than just another link in the link section.
For the quote, I think it's even more powerful to include the context directly following in the same article that
Based on historical vulnerability density, it’s likely that using Rust has already prevented hundreds of vulnerabilities from reaching production.
8 Likes
I think a better context is "There are approximately 1.5 million total lines of Rust code in AOSP across new functionality and components", but I wanted to keep the quote focused.
Meanwhile, I just had to try really hard not to leave angry comments under a StrangeLoop video, in which the presenter claimed there is no evidence that statically-typed languages prevent any real bugs from happening.
13 Likes
In the depths of a computer's core,
Where bits and bytes are stored,
Lies a tool that's often ignored
But without it, things would be floored.It's the rust borrow checker,
A guardian of memory,
Ensuring that data is in the right place
And never causing miseries.With each line of code it carefully scans,
Checking for underflows and overflows,
Preventing errors, saving the day,
And keeping the program in a flow.So let's give a nod to this silent hero,
Whose work may go unnoticed, but is never zero,
It's the rust borrow checker,
A vital part of the machine,
Ensuring our programs run clean.
4 Likes
If you built a rocket and that rocket crashes, you wouldn't update the spec of the rocket to say "it is expected to crash after reaching 3000m altitude". But if you made a typo that says the rocket should crash after reaching 3000m altitude and somehow passed review, you wouldn't add a self detonation device into the rocket just because of this either.
-- SOF3, https://github.com/rust-lang/rfcs/pull/3355#issuecomment-1343908130
2 Likes
"Rust does best when we're ambitious"
-- Niko Matsakis quoted by Yoshua Wuyts on his blog (thanks @yoshuawuyts for clearing the quote!)
6 Likes
Hah, I've pinged the person in question whether they're comfortable being quoted. I intentionally kept them anonymous so I didn't have to clear the quote in question (it's close to winter holidays, I thought they might be offline already), but welp, so much for that haha.
I'll reach back out if they get back to me with permission to attribute this quote to them.
3 Likes
Cleared the quote, you can attribute it to Niko Matsakis (:
1 Like