Inheritance is not a strict requirement of OOP. In OOP, you can always use composition, in which case the question also never arises.
Inheritance is there if you need it. It's an available option.
Inheritance is there if you need it. It's an available option.
Anyone can bring it up, but "education" isn't relevant here. It's not what was discussed in the article, or the comments.
I'm not sure I see that.
If class A and B wrap a C by composition and expose, respectively, `a` and `b`, then I still very much have the choice of which I'm building. Perhaps less so if they wrap a C by reference, so the C can be reused (it's too late at night to be sure I've thought it all the way through).