News for hackers. Stuff that matters.
Re:The Sororicide Antipattern by ubernostrum on Thursday June 01, 2017 @04:27PM (#14464254)
His argument against inheritance seems based largely on Python's weak implementation of private attributes.

No, it seems like a Python-based example of one of the well-known problems with inheritance, which applies even in languages like Java and C++ with explicit compiler-enforced visibility modifiers. Difficulty determining which class in a hierarchy is responsible for a particular member is not only a Python problem, or an "only languages without explicit public/private/protected" problem. One reason why composition is favored -- and remember, "composition over inheritance" goes back to the GoF book and earlier! -- is clearing this up.

Of course, blindly "composing" is also bad, which is what this post points out.

Re:The Sororicide Antipattern by pseudalopex on Thursday June 01, 2017 @04:51PM (#14464572)
You're right that visibility modifiers don't solve the general problem, but the author specifically says "Inheritance is bad... because it leaves each layer nowhere to put its internal state".