The Rust Evangelism Corollary
Description
A screenshot of a comment thread from a social media platform, likely Reddit, with a dark mode theme. The first comment states a well-known quote in the programming world: 'There are only two kinds of languages: the ones people complain about and the ones nobody uses.' The second comment adds a simple, impactful reply: 'And then there's Rust.' The third and final comment delivers the punchline: 'yeah that's the one where you complain about the people who use it rather than the language itself'. The humor is a meta-commentary on the developer community's perception of Rust. While the language itself is often praised for its performance and safety features, its community has gained a reputation for being overly zealous and evangelistic, constantly suggesting that other projects be 'rewritten in Rust.' This meme resonates with senior developers who have witnessed this phenomenon online and appreciate the nuanced joke that separates the technology from its culture
Comments
37Comment deleted
Rust's borrow checker prevents data races, but its community has no mutex on telling you you're using the wrong language
Rust’s real latency isn’t compile time - it’s the extra 20 minutes each stand-up takes because one engineer keeps memory-safely explaining how lifetimes would fix everything
The real borrow checker in Rust isn't the compiler - it's the community members who won't let you borrow five minutes of peace without hearing about zero-cost abstractions and memory safety guarantees
Rust perfectly embodies the observer effect in software engineering: a language so technically sound that the primary complaint isn't about borrow checker errors or lifetime annotations anymore - it's about the enthusiastic community members who won't stop telling you about memory safety at every standup. It's the only language where 'rewrite it in Rust' became such a meme that even Rustaceans had to acknowledge they'd become the thing they swore to destroy: evangelists more annoying than the segfaults they prevent
Rust’s tooling returns Result<T, E>; the discourse returns Result<T, Evangelist>
Rust: where the borrow checker wins every battle, but Rustaceans win the war of words
In Rust, suggesting “maybe Go is fine here” is an unsafe block
And C Comment deleted
There are more people hating on the existence of the language than people who even have any relation to it Comment deleted
There are developed apps and rust apps Comment deleted
there are developers and then there are people with opinions on programming languages Comment deleted
Java is shit btw Comment deleted
😂 Comment deleted
Oops May I know why? Comment deleted
ram usage, shitty language design, and it's stuck on v8, so it'll be dead in 10 years anyway Comment deleted
well - dead on desktops anyway, Android will probably continue to use the JVM Comment deleted
VMware vCloud Director (multi tenant portal for service providers) has java backend and it's only continuing to grow in functionality. Not sure if they can deny successful (but buggy... Anyway who cares?) product and start it from scratch on different language. Comment deleted
who uses that? Comment deleted
Service providers: VMware itself, Amazon, UKCloud, DataLine, Rostelecom, Aruba Cloud, IT-Grad and more of them in different countries. Customers: big companies like big tech stores which has their points of sale around the country; banks; payment systems; insurance companies; Programmers and DevOps; small and medium-sized businesses in various areas — hundreds of them in just one big public cloud. Automation systems: vRealize Automation or vRealize Orchestrator, Terraform. Comment deleted
huh Comment deleted
With microsoft backing, lol Comment deleted
? Comment deleted
Vscode Comment deleted
I didn’t know Java stuck on V8. I thought JS only. Comment deleted
Same Comment deleted
He actually mean Java8 Comment deleted
v8 is Google's js interpreter, I meant java is stuck on version 1.8 (newest is 1.17) Comment deleted
oh Comment deleted
But why? I've been seeing more and more projects using OpenJDK 11. Comment deleted
never seen a single one that requires a newer version than 8. To be fair, I try tot stay away from java in general. Comment deleted
Minecraft 1.17 fails to launch on Java 8 Comment deleted
Minecraft 1.17+ uses Java 16 (older versions used Java 8 for a long time) Comment deleted
ah, right. I still use 1.9 Comment deleted
good chioce Comment deleted
I know :P Comment deleted
performance Comment deleted
Achievements Comment deleted