Most of these exact same issues would be the same in C++, for sure similarly contrived examples could be contrived. > People, wake up! It doesn't have to be th

Most of these exact same issues would be the same in C++, for sure similarly contrived examples could be contrived. > People, wake up! It doesn't have to be this way. You've been sold Java's absurd contortions dressed in the emperor's new clothes as the default by universities and big corps for decades. I think this is a very incorrect characterization. Effective Java was required reading for me in the very late 90s (decades ago). Back then it was even argued favor composition over inheritance [1]. AFAIK you'd have to go back to the 70s or 80s for inheritance to still have a good reputation (and which at the time was certainly better than a GOTO statement). The incidental complexity was later revealed to be quite profound, and a large chunk of "Effective Java" is dedicated to explaining these complexities and why and how to avoid these. [1] https://blogs.oracle.com/javamagazine/post/java-inheritance-composition https://blogs.oracle.com/javamagazine/post/java-inheritance-...