> and basically all modern guides tell you to avoid it. If only... There's still a thriving OO-heavy mindset in much of the Java ecosystem, but less evangelica

> and basically all modern guides tell you to avoid it. If only... There's still a thriving OO-heavy mindset in much of the Java ecosystem, but less evangelical that it used to be. In other languages... Inheritance tends to be de-emphasised compared to a decade ago, thankfully. I rarely see advice to avoid it - instead moderation is advised. I think the main problem is that it is hard to explain to a learner what the pitfalls are with inheritance-heavy OO design except in the most general terms. It's something that can be quite useful when used judiciously, in the right context, but knowing when this is requires experience.