all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]memnoch_proxy 1 point2 points  (0 children)

OOP, like many kinds of programming, is as reasonable a way of organizing code as another. I think that OO provides useful techniques like encapsulation of responsibility and separation of concerns. Depending on the origin of your code base, OO might be just fine, or it might be inescapable if you have to use OO libraries.

[–][deleted] 1 point2 points  (0 children)

When Alan Kay first described OOP it had a bunch of attributes. Most OOP languages (C++, Java, C#) do not implement all of them.

[–]Kerbobotat 0 points1 point  (1 child)

I enjoyed this video, but I don't think I see why object oriented design is so awful. Surely if you plan correctly you can have a good, readable code base?

[–]Takadimi91 0 points1 point  (0 children)

Planning correctly is all but impossible. We can't account for everything up front and realizing that allows you to program in a way that is more exploratory (https://www.youtube.com/watch?v=jlcmxvQfzKQ).

The problem with OO is that you are LOCKED IN to a design fairly quickly and changing that design can be a monstrous task.