Object-Oriented Programming is Bad (2016) [video]

#1

Post by tartoran » Sat, Mar 16, 2019, 1:01 PM UTC

Object-Oriented Programming is Bad (2016) [video]
m.youtube.com

Re: Object-Oriented Programming is Bad (2016) [video]

#2

Post by holdenc » Sat, Mar 16, 2019, 1:59 PM UTC

A 44 minute powerpoint on why OOP is bad? Please refactor into separate self-contained and neatly presented topics each with their own methods for breaking down this argument.

Re: Object-Oriented Programming is Bad (2016) [video]

#3

Post by tyingq » Sat, Mar 16, 2019, 2:18 PM UTC

Here's the medium post from the same author that goes with the video: https://medium.com/@brianwill/object-oriented-programming-a-...

Re: Object-Oriented Programming is Bad (2016) [video]

#4

Post by randomsearch » Sat, Mar 16, 2019, 2:33 PM UTC

s/bad/unfashionable

Re: Object-Oriented Programming is Bad (2016) [video]

#5

Post by block_dagger » Sat, Mar 16, 2019, 2:38 PM UTC

It seems the author has not learned how to use OOP appropriately. His main argument can be summed up as “it’s hard to name things and hard to compose things” and that seems to apply to all programming.

Re: Object-Oriented Programming is Bad (2016) [video]

#6

Post by nathanaldensr » Sat, Mar 16, 2019, 2:43 PM UTC

randomsearch wrote: post #4

s/bad/unfashionable

Except it's not unfashionable. It's used by millions of programmers who just want to get stuff done. It's used by thousands of companies who don't really care how the native instructions are eventually generated. It's used by individuals and teams, application developers and library authors.

This premise of this video is flawed from the beginning and the whole thing is basically a gigantic straw man.

Re: Object-Oriented Programming is Bad (2016) [video]

#7

Post by astazangasta » Sat, Mar 16, 2019, 2:44 PM UTC

tyingq wrote: post #3

Here's the medium post from the same author that goes with the video: https://medium.com/@brianwill/object-oriented-programming-a-...

This is someone who is confronting basic limits of representation and information flow and blaming OOP. There is no one best way to organize code just like there is no one best sentence to describe a rose.

Re: Object-Oriented Programming is Bad (2016) [video]

#8

Post by ineedasername » Sat, Mar 16, 2019, 2:45 PM UTC

This seems like just another "bad" == "I prefer a different type of tool."

Re: Object-Oriented Programming is Bad (2016) [video]

#9

Post by yxhuvud » Sat, Mar 16, 2019, 2:48 PM UTC

tyingq wrote: post #3

Here's the medium post from the same author that goes with the video: https://medium.com/@brianwill/object-oriented-programming-a-...

From the post; "The problem, however, is that, while organizing program state into a hierarchy is easy, OOP demands that we then organize program state manipulation into the same hierarchy, which is extremely difficult when we have a non-trivial amount of state. Anytime we have a cross-cutting concern, an operation that involves multiple objects that aren't immediately related, that operation should reside in the common ancestor of those objects"

No, OO does not make any demands like that. You are totally free to make objects and classes out of processes and algoithms, and that is a good tool to do the kind of cross cutting concerns the article talks about.

Re: Object-Oriented Programming is Bad (2016) [video]

#10

Post by mrkeen » Sat, Mar 16, 2019, 2:48 PM UTC

block_dagger wrote: post #5

It seems the author has not learned how to use OOP appropriately. His main argument can be summed up as “it’s hard to name things and hard to compose things” and that seems to apply to all programming.

Can you please elaborate? What is his inappropriate use of OOP and how would he use it more appropriately?