Morning bathrobe rant: multiple inheritance.

Bob your rants and voice give me real green goblin vibes. enjoy!

𝑾𝒆𝒂𝒍𝒕𝒉𝒚 𝑬𝒍𝒊𝒕𝒆 𝑻𝒆𝒍𝒍𝒔 𝑻𝒉𝒆 𝑻𝒓𝒖𝒕𝒉 𝑨𝒃𝒐𝒖𝒕 𝑾𝒆𝒂𝒍𝒕𝒉𝒚 𝑬𝒍𝒊𝒕𝒆𝒔 Multi-millionaire professor Scott Galloway tells the unadulterated facts about the decline of modern capitalism and extreme inequality. ★ NEW ARTICLE ⬇️

I showed a junior dev this video. He's scared of inheritance now altogether.

Here’s a radical idea… everything in software is just concepts, applying names to them then walling off when most of the time the logic is the same no matter which pattern you use is antithetical to the fact that computers don’t give a damn about them in the first place. Use the “pattern” that does the job and the job is to write code for HUMANS that the COMPILER translates into code for COMPUTERS.

The problem with multiple inheritance is that I've found few problems best solved by inheritance and fewer still best solved by multiple inheritance. Traits and interfaces always seem to give me cleaner results than inheritance and abstract classes ever did.

Interfaces ARE abstract classes.

I think it was perfectly ok for Java language designers to make choices keeping the language simple for everyone. In contrast, C++ language designers chose to make the language so complicated that you almost need a team of lawyers only for telling you what is undefined behavior and what not.

The Java designers could have kept the language a lot simpler if they had omitted the 'interface' and 'implements' keywords.

There’s nothing *inherently* 🥁 wrong with it. The enemy is coupling and complexity. Of course if this is happening you’re operating outside of the use case scenario for multiple inheritance. Just lots of trying to save bad programmers from themselves going on in the industry today

ahaahhaah my professor is not gonna like this video

Multiple inheritance is not particularly worse than regular inheritance but regular inheritance is quite bad. Stateless interfaces should be used for polymorphism and delegation for code reuse