The Inheritance

Mary 's taxi was downstairs, so Gab accompanied her and returned to telling him that the number of media had increased. Neal immediately arranged the security guards to leave the invisible building from the underground exit. Because the rain is falling, the street is already wet and it is dark at 7 o'clock in the evening. After walking 1 or 2 blocks from the building, he managed to find a taxi. As soon as he got off the taxi at West End Avenue he met a German. When he first got home, Gabe was calling him. Freddie greeted him solemnly and they dropped the elevator.

In JavaScript, class inheritance depends on very rich and flexible prototype inheritance embedded in the language long ago, but when using class inheritance - ES6 + built on the prototype with `class` inheritance Even I will not use it. Object-oriented full power and flexibility of the prototype. In fact, you have pulled yourself into the corner and have chosen all class inheritance problems.

Class inheritance is just a complex object construct. All classes generate composite objects, but not all compound objects are generated by class or class inheritance. "Object configuration support in class inheritance" means forming complex objects from widget components rather than inheriting all properties from ancestors in the class hierarchy. Inevitable repetition problem: Because of the inflexible hierarchy, new use cases are usually implemented by copying rather than by extension, and similar classes will unexpectedly branch. Once replication is started, it is unknown which class needs to start a new class or why.

When people say "give priority to composition over inheritance", this is an abbreviation for "for combinations rather than inheritance" (the first mention to the "design pattern" of "4 GROUP"). Class inheritance has many flaws and causes many problems, so this is common sense of object-oriented design. When people talk about class inheritance, people usually ignore the class of words. It seems all inheritance is bad - but it is not so. `BassAmp` is inherited from` GuitarAmp`, 'ChannelStrip` is inherited from' BassAmp` and `GuitarAmp`. This is an example of an object-oriented design error. The channel strip is not actually a guitar amp, actually it does not require a cabinet at all. A better option is to create a new base class for inheritance of amplifiers and channel strips, but this is also limiting.