↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Ten Things I Hate About Object-Oriented Programming

The essay treats object-oriented programming as a moving target rather than a settled paradigm. It says OOP is framed in conflicting ways, from objects and classes to encapsulation and reuse, and argues that its real point is programming as modeling. It also says OOP tools and languages often expose classes in the source while hiding the runtime objects and their interactions.

Reading notes
#

  • OOP is presented as hard to define because different accounts emphasize different features, and none of them fully captures it.
  • The text rejects the idea that reuse, design flow, or a simple formula of objects and messages explains the paradigm.
  • It argues that OOP is really about letting each problem shape its own way of modeling.
  • The essay contrasts the way people praise and attack different OOP languages, especially C++, Java, and Smalltalk.
  • Classes are criticized because they are mental constructs, while programs run with objects.
  • The author says source code and runtime behavior are disconnected in OOP, and current IDEs reinforce that gap.
  • Methods are described as too fragmented for reading code efficiently, since developers spend time jumping among many small pieces.
  • The text calls for tools that let developers move between a running application and its code.
  • Types are said to create false confidence, to assume consistency the world does not have, and to struggle with multiple useful type systems.
  • Change is treated as the central problem, and context is proposed as a first-class concept that languages and IDEs should support.
  • Design patterns are described as adding complexity, with Visitor used as an example.
  • Methodologies are mocked as fear-driven, and UML is criticized because diagrams do not fail at runtime.
  • The conclusion says OOP has lasted longer than expected and that its deeper value may lie in helping manage complexity and change.