You must log in or # to comment.
In over ten years of professional programming, I have never used inheritance without regretting it.
It works great for technical constructs. E.g. A Button is a UI element. But for anything business logic related, yeah it’ll suck.
That’s wild. What did you use it for?
Some legacy Python code that already used inheritance. I had to extend it, and it was pretty infeasible to refactor the whole thing to not use inheritance. Not sure if I technically regretted that decision, but it was definitely painful, since Python inheritance makes it really hard to follow program control flow.
Non typed inheritance, what could go wrong eh. You can just ‘add’ a function to a class dynamically in python, that is so bad.
Done any C++ classes & inheritance?
It was actually typed. Python had type annotations at the time.
I only wrote C++ very early in my career so I don’t remember much, but I’m sure I at least tried some inheritance in toy games I would write. All of that code was trash though by my standards today.
Still does, but you don’t have to.
So you haven’t had much experience with oop?
I have used OOP design patterns many times, but that doesn’t mean I use inheritance a lot. I almost always reach for interfaces instead.
Well then I understand why inheritance isn’t your thing, I yet have to see an interface in need of inheritance.
This applies to firewall rules too
It might be nice to use in some very specific cases (e.g. addition-operation is a binary-operation AST node which is an AST node).
In most of the cases it just creates noise though, and you can usually do something different anyway to implement the same feature. For example in rust, just use enums and list all the possible cases and it’s even nicer to use than inheritance.
Do you include “traits” and “interfaces” under the title “inheritance”?
No because those are different things.
Composition over inheritance every day, all day
The venerable master Qc Na was walking with his student, Anton. Hoping to prompt the master into a discussion, Anton said “Master, I have heard that objects are a very good thing - is this true?” Qc Na looked pityingly at his student and replied, “Foolish pupil - objects are merely a poor man’s closures.”
Chastised, Anton took his leave from his master and returned to his cell, intent on studying closures. He carefully read the entire “Lambda: The Ultimate…” series of papers and its cousins, and implemented a small Scheme interpreter with a closure-based object system. He learned much, and looked forward to informing his master of his progress.
On his next walk with Qc Na, Anton attempted to impress his master by saying “Master, I have diligently studied the matter, and now understand that objects are truly a poor man’s closures.” Qc Na responded by hitting Anton with his stick, saying “When will you learn? Closures are a poor man’s object.” At that moment, Anton became enlightened.
Should’ve listed the source. Bad commenter.
Source: https://wiki.c2.com/?ClosuresAndObjectsAreEquivalent
(Sorry dude, my time was limited by how long I could spare poopin in-between meetings.)
Deref is for smart pointers and not for inheritance.
Also sometimes newtypes
Examples of inheritance hierarchies are always totally useless shit like this - what if a cow is an animal; What if a cow is a mammal, all mammals are animals and all mammals have a lactate() method?
Because any real life use that might come to mind would probably be related to some NDA protected database in a company.
And it is otherwise hard to think of anything at the spot, so just go with what the first example on the web-search came up with.Yeah… Wheres the AbstactAnimalFactoryManager?
I always knew Mondrian was painting cow production machines.
Separating data structure from implementation has benefits.
In languages with classic OOP classes and objects, it’s often necessary to write wrappers or adapters to allow new operations on existing objects. This adds overhead and require more code.
I wish I could take go’s interfaces and drop them into zig, and that’s all the object oriented concepts I need.
Removed by mod
Removed by mod
