getting_started/introduction/godot_design_philosophy

[giscus[bot]]

getting_started/introduction/godot_design_philosophy

Now that you've gotten your feet wet, let's talk about Godot's design. Every game engine is different and fits different needs. Not only do they offer a range of features, but the design of each en...

https://docs.godotengine.org/en/stable/getting_started/introduction/godot_design_philosophy.html

[Falco-Boehnke]

Took a bit: Inheritance and Aggregation seem similar but fulfill different purposes.

Aggregation allows you to compose a scene using other complex scenes, but keeps the scenes separate. It defines a 'has-a' relationship: A human 'has-a' set of eyes, 'has-a' nose, 'has-a' ability to hear.

Inheritance allows you to derive from a scene: A farmer inherits from the 'human' scene, therefore 'has-a' set of eyes, 'has-a' nose etc. The relationship is 'is-a'. The farmer 'is-a' human. But the farmer also 'has-a' hat and 'has-a' ability to harvest crops. Changes to the human aggregate to the farmer, but changes to the farmer aren't inherited to the human

[Grimslip]

Thank you for bringing this up. I had to go and research this further for my own satisfaction. After an hour or more down a new rabbit-hole, I now have an incrementally deeper understanding of some OOP principles.
It's a long, slow process for someone who started programming over 50 years ago (when "modular programming" was the latest best practice) to bring myself up to current thinking.

[Falco-Boehnke]

Welcome back then! :)

[Grimslip]

Thank you.