Object-Oriented Programming is Bad

Channel:Brian Will · Length:44:35 · Published:2016-01-18 · Views:2634558

Watch on YouTube

Summary

Brian Will makes the case for procedural programming over object-oriented programming, arguing that OOP's promised encapsulation and decoupling are largely illusory. He analyzes real code examples and the problems of tying data to behavior in classes.

Why HN recommends it

HN returns to it as the go-to critique of OOP, recommended for explaining the costs of abstraction better than most written arguments.

I highly recommend this video by Brian Will who does a much better job explaining this problem than I could. — HN, 2017

Programming language design · Software architecture & design

Subtitles (excerpt)

when I say that this video is probably the most important programming video you're ever going to watch it's partly because what I'm going to tell you is distinctly a minority position among programmers probably 5% or under programmers will tell you that definitively objectoriented programming is just not a good idea and in fact is going to lead you astray uh maybe you'll have another 20 30% of programmers who will hem and ha and say that it has some virtues and some weaknesses and it might be better applied to some problems than others I'm not telling you that I'm telling you definitively no objectoriented programming doesn't fit any problem and you shouldn't take it seriously this is almost certainly not what you were told in school if you attended a programming course in the last 15 years or you read most educational materials about programming the the pervasive default assumption is just well objector programming is the right way to go and it's just a settled matter so I reiterate this is probably going to be the most important video you watch about programming because it's going to tell you something you're not going to get from a vast majority of other sources first off I'm going to try and make clear exactly

On Hacker News

Looking at your top priority books I recalled a slide from one of Brian Will's videos on object oriented programming: "Object Oriented Programming is Bad" [VIDEO] . At around the 43:51 he pulls up a slide picturing several of these (and similar) books. Here is a rough quote: "I can tell you from personal experience of having read these books that you don't need to read them. They don't have answe… — jmulho, 2019-12
Code should be written first and foremost for humans to understand, and incidentally for compilers to understand. [LINK] If we can all agree about that then we have to ask ourselves if encapsulating data and behavior at the granularity of classes makes the most sense for human comprehension. In naive OO examples (Animal -> Cat) it does. In practice however, it's debatable (at best). I highly reco… — ryanmarsh, 2017-11
OOP is an industry of its own which generates a ton of incidental complexity. See "Object-Oriented Programming is Bad" by Brian Wills ( [VIDEO] ) and most of Rich Hickey's excellent videos, especially his keynote at Rails Conf 2012 where he basically told the Ruby crowd they're doing it wrong ( [LINK] ). — cutler, 2024-11
This video has a pretty good breakdown of how the "encapsulation" and "decoupling" promised by OOP is mostly a mirage: [VIDEO] — _dain_, 2023-12
Here's a really popular video that touches on many of the contentions: [VIDEO] My personal tipping point was the realization that OOP forces you to first figure out how you solution maps to OOP, before figuring out (or iterating on) how it maps to code. It creates nothing more than accidental complexity: [LINK] — zamalek, 2022-03

Related videos