Real Programmers don't write in PL/I. PL/I is for programmers who can't decide whether to write in COBOL or FORTRAN.

In recent years, there has been an ongoing debate among software developers and computer science enthusiasts about the suitability of different programming languages for specific tasks. One such discussion revolves around the question, "Are Real Programmers able to create effective solutions using PL/I?"

PL/I, or Programming Language One, is a high-level, general-purpose programming language that was developed in the 1960s at IBM. Over time, it has fallen out of favor among many developers who have found other languages more suited to their needs. The contention surrounding PL/I stems from its perceived limitations and the availability of other languages such as COBOL and FORTRAN.

COBOL, short for Common Business-Oriented Language, is a high-level programming language designed in the 1950s for business applications. It has remained popular among developers due to its ability to simplify complex business logic while maintaining readability.

FORTRAN, or Formula Translation, is another high-level programming language initially created in the 1950s. Its primary purpose was to facilitate scientific and mathematical computations, making it an ideal choice for engineers and researchers working on numerical analyses.

Given the distinct purposes of these languages, there has been much debate among programmers as to whether or not a "real" programmer should be well-versed in all three languages - PL/I, COBOL, and FORTRAN.

On one hand, proponents of having knowledge across multiple programming languages argue that this breadth of understanding allows developers to tackle diverse challenges with ease. They assert that being familiar with a range of languages grants them a unique perspective on problem-solving, allowing them to identify optimal solutions more effectively than those who specialize in just one language.

Conversely, detractors of this viewpoint counter that such an approach dilutes the depth of expertise a programmer can attain in any one area. They claim that by spreading oneself too thin, a developer risks becoming proficient in none of these languages. Instead, they maintain that focusing on mastering specific languages - like COBOL or FORTRAN - provides them with more specialized insights and skills better suited to tackling complex tasks within those domains.

The debate surrounding the use of PL/I among "real" programmers is emblematic of this larger conversation about programming languages and their respective merits. While some argue that a programmer's mastery over multiple languages demonstrates versatility, others contend that such a broad approach dilutes expertise in any given language. Regardless of one's stance on the matter, it remains undeniable that these discussions highlight the evolving nature of software development and its continued importance as a field of study and practice.