Yèn apa komposisi asring dipilohi tinimbang warisan?

Question

Accepted Answer

**Komposisi tinimbang warisan** iku prinsip desain sing sering dikutip — milih nggawe obyek kanthi **nggabung perilaku** (komposisi) tinimbang ngwarisake saka kelas dasar (warisan). Warisan nduweni kalemahan sing signifikan sing komposisi bisa ngindhari, nanging loro-lorone nduweni panggonan.

## Warisan versus komposisi

```text
INHERITANCE → a class EXTENDS another, inheriting its behavior ("IS-A" relationship):
  class Dog extends Animal
COMPOSITION → a class is BUILT FROM other objects/behaviors ("HAS-A" / uses):
  class Car { constructor() { this.engine = new Engine(); } }   // composes behaviors
→ composition: combine smaller pieces; inheritance: derive from a parent
```

## Yèn apa warisan nduweni masalah

```text
✗ TIGHT COUPLING → subclasses are tightly bound to their parent's implementation (changes
  to the parent can break subclasses — the "fragile base class" problem)
✗ RIGID hierarchies → deep/wide inheritance trees become hard to change and understand
✗ Inflexible → a class can usually only inherit from ONE parent; behavior is fixed at compile
  time; hard to combine behaviors from multiple sources
✗ Forces an "IS-A" relationship that may not truly hold; exposes parent internals
```

## Yèn apa komposisi asring luwih apik

```text
✓ FLEXIBLE → compose behaviors as needed; combine multiple behaviors; change at RUNTIME
✓ LOOSE COUPLING → objects depend on interfaces of composed parts, not parent implementations
✓ REUSABLE → small, focused components reused in many combinations
✓ Easier to change/test; avoids fragile hierarchies; favors small, focused pieces
→ many patterns (Strategy, Decorator) use composition; "favor composition over inheritance"
  ⚠️ inheritance still has valid uses (true IS-A, sharing interface) → use it appropriately
```

## Yèn apa iki penting

Ngerti yèn apa komposisi asring dipilohi tinimbang warisan iku pengetahuan tingkat senior sing berharga amarga iku **prinsip desain fundamental** sing nambah fleksibilitas lan ngerawatan, ngrefleksikan pertimbangan desain sing matang.

Prinsip "favore komposisi tinimbang warisan" sering dikutip amarga warisan, senajan dadi fitur OO inti, nduweni kalemahan sing signifikan.

Ngerti **pambedane** (warisan minangka hubungan "IS-A" sing ngluwihi induk, komposisi minangka hubungan "HAS-A" sing nggawe saka obyek liya) iku pondasi.

Ngerti **yèn apa warisan nduweni masalah** iku wawasan kunci: **sambung erat** (subkelas terikat implementasi induke, bébas owah-owahan ndobrak subkelas — masalah kelas dasar sing rapuh), **hierarki kaku** (wit warisan jero dadi angel diganti lan direti), **ora fleksibel** (biasane mung warisan siji, perilaku tetep ing wektu kompilasi, angel nggabung perilaku saka akeh sumber), lan meksa hubungan IS-A sing bisa uga ora bener.

Iku masalah nyata, signifikan sing nyebabake kesulitan ngerawatan.

Ngerti **yèn apa komposisi asring luwih apik** — **fleksibilitas** (nggabung lan nggawe perilaku minangka kabutuhan, owah-owahan saat runtime), **sambung longgar** (gumantung ing interface saka bagean komposisi tinimbang implementasi induk), **panggunan ulang** (komponen cilik, fokus digantu ing akeh kombinasi), lan nggampang owah-owahan lan test — nerangake yèn apa komposisi ngindhari kalemahan warisan.

Magenal yen akeh pola (Strategy, Decorator) nggunakake komposisi, dene warisan isih nduweni gawe valid (hubungan IS-A bener, bagéan antarmuka), ngrefleksikan pertimbangan seimbang — komposisi *asring* dipilohi, nanging warisan nduweni panggonan.

Prinsip iki fundamental kanggo desain fleksibel, ngerawatan.

Senajan "favore komposisi tinimbang warisan" iku prinsip fundamental, sering dikutip, lan senajan ngerti kalemahan warisan nyata (sambung, rigiditas, ora fleksibel) lan kauntungan komposisi (fleksibilitas, sambung longgar, panggunan ulang) — dene migateken gawe valid warisan — ngrefleksikan pertimbangan desain matang sing nambah kode, ngerti yèn apa komposisi asring dipilohi tinimbang warisan iku pengetahuan tingkat senior sing berharga — prinsip desain fundamental kanggo kode fleksibel, ngerawatan, ndasari akeh pola, lan ngrefleksikan pertimbangan desain matang (milih komposisi nalika ngerti panggonan warisan) sing dikarepake saka pengembang senior nulis perangkat lunak obyek-oriented sing dirancang kanthi apik.