The irony of this meme being posted from a platform written in rust is pretty great ngl
this post was submitted on 10 Aug 2025
832 points (95.0% liked)
Programmer Humor
25671 readers
2329 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
A platform that is doing a great job so far but which (unfortunately) isn't as relevant yet to call it a pillar of modern infrastructure. ;)
It certainly is a pillar of my mental stability.
💜 happy to know we're making it better.
Ah, me a pillar of my insanity.
I like how this takes familiarity with the original xkcd comic as a given.
Knowledge of the sacred texts is required for enlightenment.
If not, you're one of the lucky 10000.
The comic is now a mainstream meme, isn't it?
load more comments
(1 replies)
I get the joke, but rust is actually pretty heavily used in the backend of services theae days. Cloudflare, Amazon, Dropbox, just to randomly name a few off the top my head. Have pretty heavily invested it into their back ends for more reliable service.
Over the last one or two years I feel like Rust haters have gotten even louder than the Rust evangelists. For every person who declares "Rewrite it in Rust!" I see two or three people saying how they hate Rust or how pointless it is and so on.
I am convinced Rust haters are simply refusing to learn something new, consciously or not.
load more comments
(1 replies)
Yeah, this whole meme just looks like ‘I hate Rust and don't want it anywhere’
Of course, there is importance in trying it everywhere, because it shows where the language and ecosystem lacks and can evolve; but beside that, I think adoption by big companies wouldn't happen if it wasn't any good as some want to believe
Rust is fearlessly upholding the whole thing even without touching it. Incredible!
Gotta keep a distance to that dirty unsafe code!
Rust is actually awesome in many ways. No always the right solution, but nice to have in your toolbox.
Where would you say Rust isn't the right solution?
We always hear how great Rust is, but I'd be curious to know where it isn't.
Rust provides safety and protection.
Rust isn't as rapid as other options, has less library support, and porting existing code is relatively difficult.
IMO because of the workarounds you need to do to handle the memory safety, you end up with a lot more hard to solve bugs than you do with conventional languages. It should be noted however that the bugs don't end up being security vulnerabilities like they do in conventional systems.
If you have something that needs to be structurally sound and/or you have enough talented people willing to work on it, it's a great option. If it needs to be fast and cheap and you don't have a gaggle of rust developers on hand and it's already written in another language, it might not be the best solution.
I come from embedded C, so what you describe doesn't feel alien to me (minus the security vulnerabilities haha)
I much prefer working with Rust restrictions than a higher level language without hard types because I am used to it.
load more comments
(6 replies)
I great example I saw is a dev who was building on a Rust game (with the Bevy engine), and switched to Unity.
https://deadmoney.gg/news/articles/migrating-away-from-rust
Collaboration - I started this project with my brother. While he's sharp and eager, he's new to coding. Onboarding him directly into game dev while simultaneously navigating Rust's unique aspects proved challenging. We found ourselves with a steeper learning curve that slowed his ability to contribute effectively to gameplay logic.
Abstraction - While my initial motivation was the enjoyment of Rust, the project's bottleneck increasingly became the rapid iteration of higher-level gameplay mechanics. As the codebase grew, we found that translating gameplay ideas into code was less direct than we hoped. Rust's (powerful) low-level focus didn't always lend itself to a flexible high-level scripting style needed for rapid prototyping within our specific gameplay architecture. I found that my motivation to build and ship fun gameplay was stronger than my desire to build with Rust.
Migration - Bevy is young and changes quickly. Each update brought with it incredible features, but also a substantial amount of API thrash. As the project grew in size, the burden of update migration also grew. Minor regressions were common in core Bevy systems (such as sprite rendering), and these led to moments of significant friction and unexpected debugging effort. This came to a head on one specific day where I was frustrated with a sprite rendering issue that had emerged in a new release. Blake had run into the same problem at the same time and our shared frustration boiled over into a kind of table flip moment. He turned to me and said something along the lines of "this shouldn't happen, this kind of thing should just be solved" and that triggered the conversation that led to a re-evaluation. The point isn't that specific sprite problem, but that because all systems in Bevy are open to tinkering and improvement, all systems were potentially subject to regressions.
Learning - Over the past year my workflow has changed immensely, and I regularly use AI to learn new technologies, discuss methods and techniques, review code, etc. The maturity and vast amount of stable historical data for C# and the Unity API mean that tools like Gemini consistently provide highly relevant guidance. While Bevy and Rust evolve rapidly - which is exciting and motivating - the pace means AI knowledge lags behind, reducing the efficiency gains I have come to expect from AI assisted development. This could change with the introduction of more modern tool-enabled models, but I found it to be a distraction and an unexpected additional cost.
Modding - Modding means a lot to me. I got my start in the industry as a modder and I want my game to be highly moddable. Over time, as I learned more about how to realize this goal, I came to understand many inherent limitations in Rust and Bevy that would make the task more difficult. Lack of a clear solution to scripting and an unstable ABI (application binary interface) raised concerns. I am not an expert in this area, perhaps these are all easily surmounted. I can only say that I did not find a path (after much searching) that I felt confident trusting.
It sounds like Rust (game engines, and more) could use a higher level scripting language, or integrate an existing one, I guess.
I interface with low level communication protocols, mostly uart, so it fits my use case. But it is nice to see the hurdles people encounters. It tells a lot about the language.
load more comments
(1 replies)
load more comments
(3 replies)
Never used Rust but I'd like to point out the YouTube channel Low Level which covers security vulnerabilities (CVEs). He ends each video with "would Rust have fixed this?" and it's pretty interesting.
A very recent one is this: https://youtu.be/BTjj1ILCwRs?t=10m (timestamped to the relevant section)
According to him, when writing embedded software in Rust (and UEFI is embedded), you have to use Rust in unsafe mode which basically disables all the memory safety features. So in that kind of environment Rust isn't really better than C, at least when it comes to memory safety.
That's not to say Rust isn't still a good option. It probably is.
Again, I never used Rust so I'm just parroting stuff I've heard, take all of this with a grain of salt.
Rust doesn't have "safe" and "unsafe" modes in the sense your comment alludes to.
You can just do the little unsafe thing in a function that guarantees its safety, and then the rest of the code is safe.
For example, using C functions from rust is unsafe, but most of the time a simple wrapper can be made safe.
Example C function:
int arraysum(const int *array, int length) {
int sum = 0;
while (length > 0) {
sum += *array;
array++;
length--;
}
}
In rust, you can call that function safely by just wrapping it with a function that makes sure that length is always the size of array. Such as:
fn rust_arraysum(array: Vec<i32>) -> i32 {
unsafe{ arraysum(array.as_ptr(), array.len() as i32)}
}
Even though unsafe is used, it is perfectly safe to do so. And now we can call rust_arraysum without entering "unsafe mode"
You could do similar wrappers if you want to write your embedded code. Where only a fraction of the code is potentially unsafe.
And even in unsafe blocks, you don't disable all of the rust checks.
load more comments
(1 replies)
load more comments
(2 replies)
load more comments
(4 replies)
I get the meme (though why was this single unstable point - imagemagick in the original xkcd - removed? To make the left side seem more stable clmpared to the original idea?), it might be trueish atm. But with rust I feel that a lot of projects that are rewritten in rust are quicker arriving at a "finished" (or almost finished) state where they are more or less just tools being used without much discussion anymore. I guess a lot of commonly used tools already use Rust in some way, but i rarely is an issue which makes this discussion-worthy or generates enough conflict in order to raise awareness outside.
I have a hunch that open-source rust-devopment is less of a hassle as a lot of discussion about code or the quality therof is simply avoided by a stricter compiler. If the code committed compiles with rustc there's less possibility of it breaking other things in the codebase or containing hidden dangers that need to be discussed. Overall less friction, less overhead and distruction from the actual coding.
Old programs everyone agrees do exactly what they should are a perfect target for "black box" porting to a new language, where the only criteria for success are "it should function exactly like before, just more efficiently, while being more maintainable"
I'm working with some Rust right now that is 100% a big mess..
It's consistently either the Rust or the Docker components that fail to build. In fairness, it's a VERY big and complex application.
We had to use Nix to build Rust services and make containers of them. It works pretty well, except with Nix 2.29 and 2.30 where it is broken for some reason
load more comments
(2 replies)
Still waiting on that rust-based Nvidia driver. I assume it will take a few years tho.
Considering that FFI is very much a thing, I'm finding it difficulty to understand the point it's trying to make.
Yes, but with 0 blocks already, it only needs 62 more for total domination!
Wait, but I don't see how it's relevant in the smallest of ways... OOOOOH! (/s, bc obviously we all knew that already:-P)
That works great 👍
view more: next ›