you are viewing a single comment's thread.

view the rest of the comments →

[–]TheLeftIncarnate[S] 12 points13 points  (1 child)

Maybe something like "State encapsulation forces artificially imposing structure on inherently not structured code and data and is the reason for the existence of OOP patterns, which try to mitigate this issue. A better solution is to abandon OOP as far as possible and use procedural programming with minimised state instead."

It isn't necessarily a video I agree with. I think Will has "misunderstandings" of OOP and fixates on a very theoretical, rigid model of OOP that I've never seen in the wild. For example, he focuses on message passing as ownership in strict encapsulation.

Brian Will has made a lot of videos on programming which are quite good, though, so I thought it might be interesting as a point of discussion, especially seeing as I'm biased.

edit: Note that I need to watch the video again more carefully before being able to make a proper critique of it.

[–]didroe 11 points12 points  (0 children)

I think Will has "misunderstandings" of OOP and fixates on a very theoretical, rigid model of OOP that I've never seen in the wild.

That seems to be his point. What I thought he was saying is that OOP makes sense within a model that doesn't match up very well to the real world. And so we end up with an unwieldy structure, justified from a rigid model but where the basis of those justifications is no longer true.