That's perfectly fine. Nobody is forcing you to not use OOP. The video just outlines the fundamental weaknesses of using OOP as the end-all-be-all solution to

That's perfectly fine. Nobody is forcing you to not use OOP. The video just outlines the fundamental weaknesses of using OOP as the end-all-be-all solution to managing encapsulation. Namely, that it creates as many (if not more) problems than it's superficially purported to solve. IMHO, OOP is a useful design pattern for some specific classes of problems. Treating it as a cure-all ideology is self-defeating. There's a huge disconnect between creating large applications using OOP and maintaining them over the long-term. In the latter case, abstractions that get baked into an OOP-only architecture will eventually start to leak in dangerous and unexpected ways as the needs of business change over time. Short-term savings in the form of strict adherence to DRY and SRP can (and will) eventually accrue as technical debt over time. Common conventions such as design patterns, DI, and TDD minimize the negative impact but they're indicative of a bigger problem. With that said. I agree, the title is dumb and clearly detracts from the underlying message.