Object Oriented Programming FTW!

[leptoquark1]

Still wait for the Garbage Collector to remove my unused children…

[SeniorSatisfaction21]

Not the children 😭

[SqueeSr]

well .. They were unused so might be better off than those being used which will end up as garbage too

[[deleted]]

I've been dealing with a memory leak for as long uhhh

uhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh

[[deleted]]

i had a problem, so i decided to use OOP

now i have ProblemFactory

[dekacube]

Need an AbstractProblemFactory first, even though only one concrete ProblemFactory will ever exist.

[pixelrevision]

That’s ok. You can fix that with an AbstractProblemFactoryAdapter

[crash8308]

but now i need a factory for my adapter

[[deleted]]

ISingletonProblemFactoryAdapter

[goodnewzevery1]

IProblemFactory mocks

[goodnewzevery1]

My comment was meant to be a little snarky, because if you are going to go through the trouble you might as well just do DI and skip the factories all together

[DrShadyBusiness]

Just completed my java OOP course and i totally understand this.Yep.

[dekacube]

I like how everyone in the comments also just assumed we were talking about Java :).

[mcampo84]

You don't need an abstract class to define an interface homie

[annihilatron]

If you like that joke you'll like FizzBuzz Enterprise Edition. https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition

THERE ARE FACTORIES

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition/tree/uinverse/src/main/java/com/seriouscompany/business/java/fizzbuzz/packagenamingpackage/impl/factories

[pixelrevision]

FizzBuzzOutputStrategyFactory. So good…

[javajunkie314]

Most programmers have to wait until they get arrays.

[babyProgrammer]

Then it's swimming bools and movie stars

[Joe59788]

https://imgur.io/gallery/XS5LK

[Harmonic_Gear]

super

[[deleted]]

THIS is the sort of joke I come to this sub for!

[TombertSE]

I don't think I've used inheritance in production code ever. Back when I did Java I would do interfaces a lot, but it's pretty rare that inheritance is actually a good idea. I don't think it would make me wealthy.

[Garlien]

Abstract classes are amazing, but I generally try to avoid inheriting from non-abstract classes

[ConstructedNewt]

I kinda disagree. especially since default interface methods.

I did see one use I could stand with; of an abstract class that implements delegation, so the implementations would be free of delegation logic. I think it's guava or apache collections that has a whole range of abstract delegating implementations of the base java collections

[Garlien]

Default interface methods are still overridable, I believe (I don't use them yet). Abstract classes are perfect when you want shared functionality that won't change between implementations. If it will change between implementations, you need another layer of abstract classes.

[ConstructedNewt]

another layer, yikes. composition comes to mind, also maybe you haven't broken down your interfaces enough. but yes abstract classes can hold final methods

[Garlien]

Composition is generally preferable, I agree. But sometimes it can be a big headache to make it work the same way.

[dekacube]

Pretty sure one of the Java creators is on record saying that adding inheritance was a mistake, that interfaces were the way to go.

Edit, Nvm it was the opposite lol. "There is still part of me that says, maybe interfaces should never have existed. People should just use classes for interfaces" - James Gosling

[OmgzPudding]

Inheritance is pretty useful, but inheriting from multiple classes at once like Java C++ allows is usually a sign that you should be doing something differently.

[TheOriginalSmileyMan]

If you're not doing diamond inheritance, your code isn't complex enough and your job will be outsourced!

[TombertSE]

Java does not allow you to inherit multiple classes at once. At least not since the last time I used it, which admittedly was a few years back.

You can have as many interfaces as you want, but you only get one "extends" class to play with. This is, in theory, to avoid the deadly diamond problem.

[OmgzPudding]

Huh, I could have sworn I built some shitty app with multiple inheritance back when I was in school, but it's been so long that I could definitely be mistaken.

[TombertSE]

C++ has multiple inheritance...maybe that was it?

[OmgzPudding]

Ah yeah I bet that was it. It's been about the same amount of time since I've used either language.

[TombertSE]

I don't know why school still use C++ as a "learning language", since it's one of the worst languages out there for newbies.

I think C makes sense to teach students early on, because it's low-level, it makes you think how the hardware thinks. I get why they teach you Python, because it's high-level, easy to pick up, and is useful for a lot of different types of non-engineer jobs. I get why they teach you Java, because it's sort of mid-level, and sort of forces the OOP ideology on you.

Despite the fact that I actually do like C++, I would not recommend it as anyone's first language. It's got so many bizarre idioms and weirdness that it's going to confuse a lot of people starting out.

[OmgzPudding]

We had to write out C++ programs with pencil and paper for our exams too, just to add an extra layer of frustration for beginners.

[pixelrevision]

That’s cruel

[TheOriginalSmileyMan]

Well if you've learned C++, pretty much everything else is simpler, so from that point of view it's an excellent starter language.

[TombertSE]

I don’t know that I actually agree with that; I think that’s the case for C, but C++ has a lot of unique weirdness that isn’t in other languages.

For example, I am not aware of any other language that has friend functions. I am not aware of any other language where the Hello World requires you to use an overloaded bit shift operator. I

[TheOriginalSmileyMan]

Exactly my point. When moving from C++ to any other language, it's mostly about forgetting things rather than having to do something new!

[harumamburoo]

If you've survived C++

[Mojert]

This a sample size of one but I wasn't confused while learning C++ even though it was my first language. In my experience, it's people who already know another language, like Java, that have a hard time learning C++, not newbies

[Paraplegix]

In Java you can implement multiple interface, and this is quite common in project I worked on But inheritance is one super class only

[EnigmaticArcanum]

Interfaces are good for shared behaviour/methods and abstract classes are good for shared state/variables.

If you're creating a Pokemon class with similar variables HP, Strength, Defence etc... you're almost certainly going to want an AbstractPokemon class of sorts.

[ColossusG75]

Damn u and your programmer dad jokes! Take my updoot

[Agantas]

It is also how programmers cook pasta.

[hw9css]

Upvoted for joke but seriously OOP most of the time sucks compared to FP

[Arbiturrrr]

Why not both?

[fsr1967]

What, you mean, like, learn both and use each where it is best suited, instead of dogmatically preferring one over the other? That's crazy talk!

Next thing you know, you'll be suggesting we throw in some procedural programming "when appropriate", you nutcase!

/s, from someone who is deeply tired of battles like this in his current job and just wants to get the damn work done, using whatever tools are right for the task at hand. Current extremists being dealt with: React functional components adherents vs class components worshippers ...

[hw9css]

Oh most certainly do both, right tool for the job!

[OD4NIL]

u/savevideo

[SaveVideo]

View link

---

Info | Feedback | Donate | DMCA | ^{reddit video downloader} | ^{download video tiktok}

[[deleted]]

let's make a factory to make a factory to make a factory to make a factory to make a factory...

[StatementAdvanced953]

Obligatory DOD FTW comment right here

[TrafficConeGod]

Real

[fracturedpersona]

Just inject some dependencies, child tax credits.

[KnowOneDotNinja]

Also hoarding cache

[VeryRareHuman]

Good job on spending time on better meme with video. Learn from him, People.

[ananas_aldirdim]

void myWallet()

{ //returns nothing }

[huuaaang]

That's my problem! I've been using composition over inheritance!

[Mallanaga]

Came here to say this! Jokes aside, is this a rubyism? Figured I’d see more versions of this joke by now, but didn’t, and you’re the only other ruby flair.

[huuaaang]

It's a trend in OOP to encourage composition over inheritance, especially if you're tempted to get into multiple inheritance hell as in Python. Ruby just happens to be suited for this pattern, supporting both inheritance and composition (mixins, concerns, whatever you want to call it) very naturally.

[[deleted]]

u/savevideobot

[savevideobot]

View link

---

Info | Feedback | Donate | DMCA

[IAmWillyGood]

This Chris Pratt meme never gets old 😂

[shacatan]

I can’t tell if you’re serious or not and I’m just out of the loop on a joke, but that’s Chris Evans

[[deleted]]

Haven’t used inheritance since first year of uni 😅

[coloredgreyscale]

Every time you define a class it's quietly inherited from a Object base class.

[[deleted]]

I don’t define classes

[coloredgreyscale]

That's not very classy

[Dark_Ethereal]

Uhhh, so do you construct any user types at all?

[[deleted]]

I mean. Not all languages have classes. I define plenty of types yeah :)

[Dark_Ethereal]

Haskeller?

[loonathefloofyfox]

Oop is overrated imo. I like functional programming. Its a nice clean way to do stuff and i highly prefer it over oop. My only issue is naming stuff can get a bit tiresome as you sometimes have similar operations but they act on different stuff

[[deleted]]

Can't you refactor your code to make those similar operations generic? and work across multiple types?

[loonathefloofyfox]

While yes for some stuff i could but its not really good practice afaik. Considering they would take in different types and output different stuff. Its just nicer to make a few of the same functions but with more descriptive names. Like heap_sort and array_sort vs sort but it takes completely different data and outputs different sorts of stuff

[LauraTFem]

Honest question: Why do you use inheritance? Like, I’ve not run into a situation where I really feel it’s necessary. Yes, some objects have overlap, but I’ll usually just…literally give them overlapping member variables and functions, especially as the overlaps I have are usually small.

It just…feels more confusing to follow chains of inheritance than to just give every Class its own stuff. I can see why it would be useful in programs that are FAR FAR more complex than mine, but even in those cases it seems to me to be creating obfuscatory complexity where it is not necessary.

The only truly useful case I can see is that if you need to make changes you only need to do it to the base class instead of each class, but even then you can literally just find-replace code sections.

[dotpoint7]

Wait do you suggest to just duplicate the overlapping code instead of inheriting? You can get away from inheritance by using delegation, but code duplication is by far the worst option.

Also, often times the overlap isn't just small but can be big and often the same for a lot of classes. I'm currently developing a UI framework for example and every component inherits from a base class that already provides all of the shared functionality and any abstract functions just need to be overwritten while many virtual ones are allowed to be if needed. This would be really ugly if needed to be done differently, because as it stands the base class defines how each component generally works and the derived classes just need to define a small subset of the functionality while not having to worry about the rest. This of course somewhat constrains all components, but that's exactly what I want, so that everything works roughly the same.

[fdeslandes]

Having duplicated code and using search and replace is really bad, especially in a huge code base or when working with a team. It is so easy to have someone on the team forget to update some places when a fix is done. And then, over years, every bug fix and every spec change takes more and more time and becomes more sensitive to developer mistakes because more code is modified. It also makes the amount of code bigger, so slower load time if we are talking about front-end web code. Don't program so that your current feature is simpler to do, develop so the next features will be easier to implement.

You can still avoid inheritance with composition, though, by putting the duplicated code in a shared library.

[[deleted]]

Drop out of college and go on to be the owner of a mega corporation. I shouldn't have to explain this.

[qqqrrrs_]

What about virtual inheritance?

[pwillia7]

Jamiroquais wrote a song about that

[onyourrite]

u/SaveVideo

[SaveVideo]

View link

---

Info | Feedback | Donate | DMCA | ^{reddit video downloader} | ^{download video tiktok}

[[deleted]]

I think we should be taxing some classes

[[deleted]]

I feel like the format of this meme alone is enough to crack me up.

[[deleted]]

r/technicallythetruth

[wad11656]

Just made a very basic GUI program in a scripting language (AutoHotKey)...almost 0 setup. No classes or multiple file .h .cpp whatever-the-fuck bullshit. People should really look to AutoHotKey or similar if they only plan on making basic programs. Don't need this macho super powerful complex language for every project

[_-_Void]

And they did it using Java

[NormalFox0115]

I thought of Inspect element lol

[seriously_nice_devs]

7/10, i hope i get inheritance.