The Difference between ECS and OOP #rustprogramming #indiegamedev #gamedevelopmentcourse

Let's break down the core differences between Entity-Component-System (ECS) and Object-Oriented Programming (OOP). For programmers looking to understand game development paradigms, this short clip distills the essence of ECS and OOP. Dive in to see which might suit your next project!

[LemmonTea]

I would love to see a video about this!!! You’ve peaked my interest

[JXQU]

Severely underrated. Great editing, great explaination!

[CG-bhvm]

Thx for explaning, I was needing that to understand the basic from basic about ECS.

[LoesserOfEvils]

I would love to see a video about the entity component system.

[ensuretime]

Old school POO using Aggregates is beautiful

[PriyamGhosh-ro]

Please create a detailed video on C++ ECS

[samob-tzfw]

Proper ECS like Bevy is so freaking hard..

[quaker]

ECS is blazingly fast but make sure you know what your getting yourself in for. Everything is accessed via arrays and it can be quite difficult to program once you need a lot of crosstalk between entities. Also, unless you need thousands of entities to be updated every frame it's better to have a Unity style component system which is slower as it's looser memory wise but it's much easier to reason with.
Whichever system you use though make sure you can also use global entities/scripts that always persist and are easy to grab and interface with. They are very handy for orchestrating the seperate parts of the game like Resources, Input, UIManager, LevelManager, Game, etc..

[Lucianovianasouza]

Yes, I would like to know about the difference between OOP and DOD and ECS, especially about what you said in the comment above "Is this the same as Data Oriented Programming?", with "entity=velocity" and "attribute=value" and for DOD (Data Oriented Programming/Design) would it be like a "key/value" of a map?

[brandonblue]

So you're not making any objects of these structs are you? I was thinking you made an instance of a struct and made that a member.

[mohammadanton]

Turning on the bell and waiting for your new upload :D

[grimlockfgz_]

would this not be the same thing as OOP ? just not in the same file ?

[Justplaying]

This is just objectively oriented programming

[Adrian]

simple ECS is the way to go. just go really small with the granuality and your good to go :)
killable, bleedable, hitable, fkable... so on...

[fuzzy-]

Is this the same as Data Oriented Programming?

[kolosso]

I've been using this pattern in my project, but I just can't help but feel this structure is too rigid and awkward. It makes sense for these simple examples with a transformComponent, but once you have a bunch of really unique entities (like a "Zombie", or "Torpedo") you have to start doing weird things like having ZombieComponents or TorpedoComponents. And unless you're using something like a sparse array, it's going to mean a lot of unused space for every entity that doesn't have those components.

[cheerwizard]

This architecture is too complicated if you want to make a complicated game with lots of entity connections. Sooner you get their, sooner you will understand that.

[Sturm]

No sir, that's not how it works. Now you gitta do the video

[adamrushford]

I tyhought this was a video about this... ffs

[ZettaiKatsu]

thanks for the editing and comments. Your accent is not easy to understand for non-natives.