Before the 360: A World of Chaos
To understand why the System/360 was so radical, you have to picture the computer industry of the early 1960s. It was a chaotic landscape. A company might buy a computer from IBM, but when they outgrew it, the next, more powerful IBM model was completely
incompatible. All of their software, painstakingly written for the first machine, was now useless. They had to start from scratch, rewriting every program and retraining their staff. It was enormously expensive and frustrating for customers. This wasn't just a problem for customers; it was becoming a major problem for IBM itself. The company maintained multiple, entirely separate product lines for different needs—small business, large business, small scientific, large scientific—and none of them could share software or parts. Supporting these distinct, incompatible families was becoming unsustainable.
The $5 Billion 'Bet the Company' Gamble
In 1961, IBM secretly convened a task force to solve this problem. Their conclusion was radical: scrap everything. Instead of maintaining separate lines, they proposed creating a single, unified "family" of computers. On April 7, 1964, IBM announced the System/360, a range of machines of varying power and price. The magic was that software written for the smallest model would run, without changes, on the largest one. This concept, called forward and backward compatibility, was revolutionary. It meant a company could start with a small, affordable system and upgrade as they grew without throwing away their software investment. But this was an immense risk. The project's cost ultimately swelled to $5 billion—more than was spent on the Manhattan Project and, at the time, nearly double IBM's annual revenue. CEO Thomas Watson Jr. famously called it a "bet the company" decision.
The Birth of Software as an Industry
The most profound consequence of the System/360 was the separation of hardware and software. Before the 360, software was essentially disposable, tied to a single machine. Because the 360 family shared a common architecture, programs suddenly had a life beyond one piece of hardware. For the first time, you could write a program knowing it could run on a whole range of computers, and even on future models. This decision created the very idea of a commercial software industry. It also established the 8-bit byte as a standard, a fundamental building block still in use today. The project's software development was famously difficult, leading to delays and inspiring Fred Brooks' seminal book on software project management, "The Mythical Man-Month," but its architectural success was undeniable.
The Blueprint for a Platform Ecosystem
The System/360 did more than just sell computers; it created the first modern technology platform. By establishing a stable, well-documented architecture, IBM enabled other companies to build products for it. A market for "plug-compatible" peripherals—like printers and storage devices—sprang up, often offering better performance or lower prices than IBM's own. This ecosystem made the S/360 platform even more valuable and entrenched its dominance. This model—a central platform that others can build upon—is the same strategy used by today's tech giants, from the iPhone's App Store to the cloud platforms of Amazon and Microsoft. The S/360 wasn't just a product; it was a business model that proved compatibility and scalability were what customers truly valued.
