this post was submitted on 03 Jul 2023
100 points (96.3% liked)
Programming
17381 readers
523 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's still cool. Ain't nothing wrong with what ain't broke. Imagine programming without inheritance in many languages. Inheritance is another tool, to perform another task. Don't be afraid to learn any tool in your toolbox. And don't sweat about problems you may never have either. And have some things inherit, you're in good company still
I've been senior for quite some time now, I know when to use what (most of the time) and yeah, inheritance has its place, though I don't use it often because most of the time it simply isn't the right thing to do.
In my experience, inheritance is really handy in the right situation. But far more often, inheritance is just a quick way to code yourself into a corner or just a waste of mental energy in the wrong place.
I can think of maybe 1 or 2 places where inheritance makes sense, and I haven't encountered these in the last 5 years... (not counting implementing interfaces of course, which definitely makes sense). In all other cases inheritance is IMHO a bad decision (why I think it should not be a thing in programming languages, because it leads someone to write bad code, as it seemed to be the right thing to do...).