The Genesis of Object-Oriented Programming (OOP): A Historical Overview – BrightMarbles

1. Introduction

Welcome to "The Genesis of Object-Oriented Programming (OOP): A Historical Overview," where we delve into the origins and evolution of one of the most influential paradigms in modern software development. In this blog, we’ll explore the key milestones and groundbreaking contributions that shaped the landscape of object-oriented programming. From the early concepts of Simula to the birth of Smalltalk and the transformative emergence of C++, we’ll trace the lineage of OOP and uncover the remarkable insights from visionary pioneers. Join us on this captivating journey through time as we unravel the fascinating history behind OOP.

2. The Triad of Programming Paradigms

The renowned software engineer, Robert C. Martin, affectionately known as ‘Uncle Bob’, once postulated that there are three fundamental programming paradigms that form the bedrock of software development: Structured programming, Functional programming, and Object-oriented programming. As articulated in his seminal book, "Clean Architecture: A Craftsman’s Guide to Software Structure and Design," [3] these paradigms were conceived during a transformative decade – the latter half of the 1950s and the early half of the 1960s.

According to Uncle Bob, these three paradigms are likely to be the only ones we will ever unveil. His argument pivots on the notion that each paradigm introduces constraints, providing guidelines on what we should refrain from doing. Furthermore, any emergent paradigm will similarly enforce new limitations. One of the keystone arguments bolstering his belief that the existing paradigms are the only ones we will ever stumble upon rests on the historical record. Quite simply, we’ve seen no new paradigm materialize in the past half-century.

Before delving into the fascinating historical evolution of the Object-oriented programming paradigm, it’s worth taking a moment to revisit the landscape of software development prior to its advent. Doing so will allow us to better understand the factors that instigated the genesis of Object-oriented programming and catalyzed its subsequent rise to prominence.

2.a Structured Programming: Algorithms and Control Flow

Structured programming pivots around crafting a suite of procedures to tackle a specific problem. Once the optimal procedures, or algorithms, have been established, the next course of action involves determining the most efficient way to store data. Notably, this ideology is embodied in the title of Swiss computer scientist Niklaus Wirth’s book, "Algorithm + Data Structures = Programs."

Essentially, structured programming is the art of software development utilizing control flow elements such as conditionals (if-then-else) and loops (for and while), code block structures, and coroutines. The code block structure allows for multiple instructions to be interpreted as a singular entity.

Structured programming rose to fame through "The Structured Program Theorem," commonly referred to as "The Böhm-Jacopini theorem", and the influential work of Edsger Dijkstra. The theorem, published in 1966 by Corrado Böhm and Giuseppe Jacopini, posited that all programming tasks can be logically executed using only elementary structures: sequence, selection, and iteration.

In 1968, Dijkstra popularized the term "structured programming" and argued vehemently against the misuse of ‘goto’ instructions, likening them to the creation of a "spaghetti code". His groundbreaking research, published in an open letter to the Communications of the ACM magazine, asserted that the number of software errors correlated directly with the frequency of ‘goto’ instruction usage. Initially titled "The case against the goto instruction", the letter stirred a passionate debate about the use of the ‘goto’ instruction after being renamed by editor Niklaus Wirth to "The goto instruction is considered harmful."

Early programming languages that employed structured programming principles include ALGOL and Ada. To encapsulate the essence of structured programming, Robert C. Martin stated, "Structured programming imposes limitations on the direct control-flow transfer." [3]

2.b Functional Programming: Harnessing the Power of Mathematical Functions

Functional programming is grounded in the principles of lambda calculus, an abstraction introduced by Alonzo Church in 1936. Central to lambda calculus, and consequently functional programming, is the immutability of symbol values. The first functional language, LISP, was developed by John McCarthy at the Massachusetts Institute of Technology in the 1950s. LISP functions were defined using Church’s lambda notation, further extended with additional functionality under the label name to enable recursive function calls.

In the functional programming paradigm, functions are treated as first-class entities. That is, they can be named, passed as arguments to other functions, or...