102
The Tragic Death of Inheritance (avivcarmi.com)
submitted 3 years ago by to c/programming@programming.dev
52 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 3 years ago (2 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 9 points 3 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 3 years ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 3 years ago

    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...).

  • permalink
  • fedilink
  • source
  • parent