technologybriefs
10:14in productionCh. 1 · A DOS replacement, not an upgrade/ 10:14 · ceiling 15 min
Software · Systems

OS/2

1987

OS/2 wasn’t killed by bad code—it was strangled by incompatible ambitions.

OS/2 was a technically sound but commercially stillborn operating system. It enforced protection, abstraction, and stability where DOS could not—but its architecture assumed vendor alignment that evaporated in 1990. Its failure wasn’t architectural; it was political, economic, and ecological.

Chapters & takeaways4
  1. 1:06
    A DOS replacement, not an upgrade

    OS/2 was built to replace DOS—not extend it—and required protected mode on the 80286 to do so.

  2. 2:56
    DOS in name, protected mode in practice

    It preserved DOS compatibility through naming and 'Family Mode', while abstracting hardware access via APIs like VIO.

  3. 4:36
    The split that doomed the partnership

    Microsoft abandoned OS/2 in 1990 over positioning against Windows 3.1—leaving IBM to build 2.0 alone as a 32-bit system.

  4. 6:17
    Twelve years of diminishing returns

    OS/2 shipped in 1987, peaked with Warp 4 in 1996, and received updates until 2001—then vanished.

Worth your time?

No. The brief is enough.

2.5/ 5
What works
  • protected-mode multitasking
  • VIO abstraction
  • HPFS reliability
  • Workplace Shell consistency
What does not
  • scale
  • compete
  • survive
Study it if
  • historians
  • retro-computing engineers
Skip it if
  • developers
  • enterprises
  • end-users
The written brief1 min read

What it is and the problem it solves

OS/2 was a proprietary operating system co-developed by IBM and Microsoft to replace PC DOS. It solved the instability and memory limits of real-mode DOS by enforcing hardware abstraction and process isolation on the 80286.

How it works

OS/2 ran in protected mode on the Intel 80286, isolating applications from hardware and each other. It used APIs like VIO to handle video and input without BIOS calls. System calls mirrored DOS conventions—prefixed with ‘Dos’—and supported ‘Family Mode’ text applications that ran on both OS/2 and MS-DOS.

What works

Protected-mode multitasking worked reliably. HPFS (introduced later) offered better disk resilience than FAT. The Workplace Shell (in Warp) delivered a consistent, object-oriented UI. VIO enabled safe, hardware-abstracted console I/O.

What does not

It did not scale beyond niche technical users. It failed to displace DOS or Windows despite superior memory management and stability. Its application ecosystem never matured beyond utilities and vertical business tools.

What it changes

It proved that a robust, preemptively multitasking, object-oriented desktop OS could run on commodity x86 hardware—but only if vendors coordinated tightly. Its collapse cemented Microsoft’s control over the PC platform layer.

Is it worth your time

No. It demanded more memory and hardware than DOS or early Windows, had negligible third-party software support after 1990, and offered no path to enterprise or consumer adoption once IBM went solo and Microsoft pivoted to Windows.

Same field · Software4 of 102
10:03
Go (programming language)Robert Griesemer, Rob Pike, Ken Thompson · 2009Go is a statically typed, compiled programming language designed in 2007 by Robert Griesemer, Rob Pike, and Ken Thompson at Google to improve programming productivity for multicore, networked machines and large codebases. It combines static typing and runtime efficiency like C, readability and usability like Python, and high-performance networking and multiprocessing. Publicly announced in November 2009 and released as version 1.0 in March 2012, Go emphasizes simplicity, safety, and developer tooling — especially around concurrency via goroutines and channels, packaging, testing, and deployment — while deliberately omitting features like inheritance, assertions, pointer arithmetic, and implicit type conversions. Its design reflects a focus on the software development process itself rather than just language syntax or semantics.
9:44
Apache CassandraFacebook · 2008Cassandra is a distributed, wide-column database built for write-heavy, multi-datacentre workloads. It prioritises availability and scalability over consistency. It requires upfront schema design aligned to access patterns. It was developed at Facebook for inbox search and released open-source in July 2008.
10:00
Apache HadoopYahoo · 2006Hadoop is not a database or a query engine. It is a fault-tolerant batch-processing substrate built for scale, not speed or simplicity.
10:34
Amiga 10001985The Amiga 1000 is not defined by what it promised, but by what it delivered on day one: a working, shipped, ROM-locked implementation of preemptive multitasking — alongside deliberate physical design choices that treated the case as functional infrastructure. Its limitations are architectural, not aspirational.
Up next in Technology

Package manager

· 9:37

Package managers don’t solve dependency hell—they formalise it.

9:37