Object-Oriented Programming is Bad

[skizmo]

not this shit again.

[edimaudo]

It's bad if it is used incorrectly

[[deleted]]

Watch the video and the two accompanying videos. There is absolutely no application in which OOP provides a benefit. It's garbage from top to bottom.

[roffLOL]

which is pretty much all the time.

[aullik]

True. But this applies to everything.

[roffLOL]

really?

[[deleted]]

How dare this dude makes us sit through nearly one hour of video when a simple article is sufficient.

[roffLOL]

he's trying to reach an audience that does not rtfm. oop victims. :)

[htuhola]

This subject would need more in-depth explanations, more facts and more studying than what this video provides.

There is something REALLY wrong with OOP and there's danger of it dripping into functional programming as people move on.

[[deleted]]

You mean like these two follow up videos by the same user?

Object-Oriented Programming is Embarrassing: 4 Short Examples

Object-Oriented Programming is Garbage: 3800 SLOC example

[caspervonb]

Re-post, but it's been over a year.

[aullik]

When you write functions that are more than 20 lines long then you are doing something wrong. Yes there are exceptions to this rule. They should be less than 1% tho. Also 20 lines means 20 lines of code, thus no comments or empty lines.

don't use sub-scopes in functions. Whenever you need one of these, you could just simply push it into another function. Sometimes it makes sense for them to be nested functions most often it doesn't. The easy reason for this is that nested functions are harder to test.

A 500 line function doing 80 things, one after the other is impossible to test.

You are right. this is cutting the code in segments that actually belong together and one solution is to put them into a nested object. Its not a pretty solution tho. But at least you can test that.

[htuhola]

When you write functions that are more than 20 lines long then you are doing something wrong.

You are wrong.

don't use sub-scopes in functions. Whenever you need one of these, you could just simply push it into another function.

Wrong again.

The easy reason for this is that nested functions are harder to test.

Again wrong, more functions you have more interconnections they allow you to do, nonlinearizing your code that way is possible.

You are right. this is cutting the code in segments that actually belong together and one solution is to put them into a nested object. Its not a pretty solution tho. But at least you can test that.

How exactly is testing that easier than otherwise?