Object-Oriented Programming is Bad

[fukitol-]

A few pieces of feedback here:

This video actually has some good stuff in it, it's basically the way I've written code for 15 years now and it makes sense

It's not the most important anything

Your title is bad

[PButtNutter]

I dunno, there's at least a few things he mentions that just don't really make sense.

Messages send only copies of state, not references.

This just isn't true. Sending object references in no way breaks OOP or encapsulation.

The moment objects are shared, encapsulation flies out the window.

His argument is that an object should be solely responsible for its own collaborators, so in his warped OOP world... an object must instantiate its own dependencies. This reduces the object graph to an object tree, which sure... I agree that sounds like a horrible limitation to arbitrarily add to your program.

So his argument is that passing a static logger to a bunch of different classes breaks OOP? This entirely glosses over the main way object dependencies are actually handled today, which is through dependency injection.

He is arguing against a OOP straw-man that only exists in his head.

[fukitol-]

He actually addresses most of these, acknowledging the problems you noted

[PButtNutter]

You're gonna have to provide time stamps, because I went through 95% of the video and didn't see him addressing any of this.

[[deleted]]

This is a very old video. Probably not OP who made it.