-10.6dB❌ -6.8db✅

@@ExplosionPower1387 What do you mean

@@Ddos2212 ABOUT LOUDNESS YOU TALKING

​@ExplosionPower1387 no need to scream random youtube user

hopefully youre being sarcastic

well I just store each entity in its own array so things are kinda well placed in memory

​@@lowlevelgamedev9330why not do vector

why not a vector of Entity

@@lowlevelgamedev9330 iirc the "Entity" in an ECS is just the ID used to index into the arrays of components that it has. Such that when you update "Position" for example, you traverse the array of all positions to update them, and the data is all contiguous in memory - hence the performance gain. If each object has its own data, and you have an array of objects, I'm pretty sure it's not really an ECS at that point. That's just OOP with good use of composition over inheritance, but you don't gain the cache coherence benefits of contiguous memory = much less cache misses

@@arandomguythatdoesntpost That's not how an ECS works, it's a bit complicated to say. Contiguous memory is what makes ECS fast. The "Entity" part is just an ID that knows which arrays (components) it has. Cache coherence is why ECS is fast, using contiguous arrays.

I don't plan on making a cpp tutorial

maybe later, rn I don't plan one because it takes a lot of time and it doesn't make that many views

but I will make some beginner topics tutorials like the pointers one 💪

@@lowlevelgamedev9330 Oh... but hey! I know how to make it get views!

best part 😂

Because C++...

well that's not the point, the point of templates is to be able to do what I showed in the end, make a function that can work with anything, if you just need float and int yes you would do that

@@lowlevelgamedev9330 sadly that's how they are used in some codebases

well they are totally different and I know how to use both and I would say that templates are worse simply becausw they have a ton of rules with move semantics and decay and forwarding and stuff, yes zig is better for this kinda stuff 💪

yes tho I have never tried concepts, fortunatelly, for what I do here I don't need concepts or sfinae, so things are rather simple

@@lowlevelgamedev9330 Concepts are great to limit your template parameter options or to create interfaces that don't use virtual polymorphism, so I would strongly argue anybody that uses virtual polymorphism should look at them

@@lowlevelgamedev9330 Concepts are great for limiting the allowed inputs into your templates (much easier than with SFINAE), and they are fantastic for creating interfaces instead of using pure virtual methods that you override, which are more expensive (and again, easier than SFINAE). For example: say that you have an IAnimal interface with the methods Speak and Move, simple stupid, but it works, you could do: class IAnimal { public: virtual ~IAnimal() = default; virtual auto Speak() -> void = 0; virtual auto Move() -> void = 0; }; class Dog : public IAnimal { public: auto Speak() -> void final { std::cout void final { std::cout Speak(); animal->Move(); } int main() { IAnimal* dog = new Dog(); GiveMeAnimal(dog); delete dog; } Or you can simply use concepts and do even better, and using the stack instead of the heap: template concept IAnimal = requires(T a) { { a.Speak() } -> std::same_as; { a.Move() } -> std::same_as; }; class Dog { public: auto Speak() const { std::cout

1