News for hackers. Stuff that matters.
Re:The Case Against OOP Is Wildly Overstated by fdupress on Friday July 31, 2020 @02:03PM (#24011559)
A good example would be a complex state machine, where you rely on the fact that the state is only modified by the state machine code to make sure it remains well-formed, and the control-flow itself heavily relies on the state being well-formed (think of a TLS session, for example).

But then again, what you want there is modularity, which OOP provides, but is also well-supported in other paradigms.

Re:The Case Against OOP Is Wildly Overstated by Gibbon1 on Friday July 31, 2020 @04:32PM (#24013640)
Yeah but you don't need OOP to do that. See opaque pointer's in a number of non OOP languages.
Re:The Case Against OOP Is Wildly Overstated by billisonline on Saturday August 01, 2020 @03:27PM (#24023189)
You don't need OOP to do anything! But in the state machine example, it provides a coherent and readily understandable metaphor (object modifies its own private state; callers can tell it what to do but not how) for the task at hand. Isn't that the goal of a programming paradigm?
Re:The Case Against OOP Is Wildly Overstated by augustk on Friday July 31, 2020 @05:07PM (#24014108)
These are called Abstract Data Types.
Re:The Case Against OOP Is Wildly Overstated by garethjrowlands on Saturday August 01, 2020 @09:40AM (#24020355)
This paper describes the differences between objects and ADTs, https://www.cs.utexas.edu/users/wcook/papers/OOPvsADT/CookOO...