made in gimp, with <3
Context for actual rust programmers
I was having massive beef with the rust compiler yesterday, every cargo check takes 20 seconds.
And then look at the three functions below, only one of them are Send, if you know why, please let me know.
(Note: value that is not Send cannot be held across an await point, and Box<dyn Error> is not Send)
async fn one() {
let res: Result<(), Box<dyn Error>> = do_stuff();
if let Err(err) = res {
let content = err.to_string();
let _ = do_stuff(content).await;
}
}
async fn two() {
let res: Result<(), Box<dyn Error>> = do_stuff();
let content = if let Err(err) = res {
Some(err.to_string())
} else {
None
};
drop(res);
if let Some(content) = content {
let _ = do_stuff(content).await;
}
}
async fn three() {
let content = {
let res: Result<(), Box<dyn Error>> = do_stuff();
if let Err(err) = res {
Some(err.to_string())
} else {
None
}
};
if let Some(content) = content {
let _ = do_stuff(content).await;
}
}
Rust output is bad? I feel like it’s one of the best in terms of telling you where you got things wrong. Nix output when you accidentally get infinite recursion is so bad.
Come to think of it, Nix fits all three better than Rust.
Ah yes, the good old random pile of unclear errors because you forgot to add the file in git thanks nix
People who’ve never used Rust or only used it once and couldn’t grok it like to meme that Rust is bad to cope.
Yes, preferring a language that’s easy to read and therefore easy to maintain over a language like Rust is definitely coping 🙄
preferring Rust over Rust? what do you mean?
do you think loosely typed python is easy to read and maintain?
I’ll stick with Go TYVM
Yeah, like, who would ever want to
stuff1()?.map(stuff2);It’s much better to just:
err, value = stuff1(); if err == nil return err, nil; if value != nil stuff2(value);And you might even:
for a in vec { vec[a] }I totally agree, that Go snippet is absolutely more maintainable. Though you forgot the curly braces and the semicolons are unnecessary.
Though you forgot the curly braces and the semicolons are unnecessary.
Yup. These are pretty big issues. But there are also some minor, trivial, purely-preference-based issues - like returning an error if
err == nilinstead of when it isn’t.
I get that it’s supposed to be a meme, but aside from the first one these aren’t even rust stereotypes. Is this a meme specifically for people who haven’t used rust, know nothing about rust but have maybe heard that it’s a programming language?
Yeah, part of the point of Rust is that it does exactly what you tell it - sometimes to the point of absurdity. No implicit casting for instance.
I mean Rust is definitely known for long compilation times but yeah otherwise I am not sure how any of this is Rust-specific. Maybe by “doesn’t do what you tell it to do” they mean the borrow checker and strict compile time checks…?
i’ve edited the post content for context, and a small puzzle for rust programmers
I was actually wondering if this was supposed to be about a specific problem someone has with rust (not like I haven’t gotten stuck on some weird corner with rust before), but looking at the meme, that seemed unlikely to me. Thanks for the context.
output makes no sense
C++ template errors enter the room
Template errors make sense as long as you carefully read the entire error, but nobody has ever actually done that.
You are saying that the error messages terminate at some point?
Well, yeah, templates won’t recurse beyond 1,024 levels.
That’s an implementation-defined behaviour.
I like to pretend that gcc is the only compiler
Just a guess, but are you missing
+ Sendon your error type?I love the rust compiler, it makes debugging so easy
cargo() { cargo $@ echo So how you doin\' today? }Fixed
I thought the rust compiler was supposed to be polite and helpful (unlike gcc, or nix).
It is, this meme is just trash.
gcc was unhelpful a couple decades ago. I’ve found it to be rather helpful in recent years.
Yeah, recent versions of GCC have gotten a lot better. I suspect it’s actually because of languages like Rust raising the bar.
No, Rust came later.
they didn’t say otherwise
They literally did. They theorized that Rust influenced GCC’s improved error messaging. That could not have happened if GCC improved their error messaging prior to the existence of Rust.
But GCC did not improve their error messages (much) prior to Rust, despite Clang’s error messages comparing favorably to GCC even before Rust 1.0 was released, as for example discussed in
https://gcc.gnu.org/wiki/ClangDiagnosticsComparison?action=recall&rev=1
Rust itself is 14 years old, slightly older than above wiki page, and even back then it had great error messages, though they’ve also improved since. Here’s a fun site where you can see how error messages have evolved through Rust’s life:
https://kobzol.github.io/rust/rustc/2025/05/16/evolution-of-rustc-errors.html
It’s only very recently that GCC has started to catch up, for example with some nice improvements in GCC 15:
https://developers.redhat.com/articles/2025/04/10/6-usability-improvements-gcc-15
Oh, guess my mental timeline is wrong!
Oh god nix output
Deterministic: ✅ ❌
Deterministic when hit by that weird cosmic ray: ❌❌
/jk
