technologybriefs
SubjectsAll subjects on briefs.cloud →
Saved
Software · Systems

OS/2

1987

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

Worth your time?2.5/5No.The brief is enough.What works, what does not, who it is for ↓
10:14in productionCh. 1 · A DOS replacement, not an upgrade/ 10:14 · ceiling 15 min
4 chapters · 10:14Ceiling 15:00

The brief is written and checked. The video joins this page when it is cut.4 chapters · 1 min read · 10:14 planned

Read the brief

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.

SoftwareSystemsComputingFailureHardwareComputing across the network →
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.

1 more chapterFewer chapters
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
Who should study it, and who should skipHide who it is for
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 114
10:18
PostgreSQLUniversity of California Berkeley · 1996PostgreSQL is a free and open-source RDBMS that solves the problem of building reliable, scalable, and standards-compliant relational data systems without vendor lock-in. It emerged from Berkeley’s POSTGRES project in 1985 to address limitations in contemporary databases, especially Ingres’ lack of SQL support and type extensibility.
10:46
Neo4jNeo4j Inc. · 2010Neo4j is a graph database built for relationship-heavy workloads. It delivers expressive querying and transactional safety—but horizontal scaling, vector search, and unified standards arrived over a decade after launch. Its value is real, but bounded by what it ships—not what it promises.
9:22
WebAssembly2015WebAssembly standardises portable binary code execution. It works well for C/C++ in browsers and emerging non-web contexts. It does not yet deliver on its full promise for high-level languages or parallelism. Its value is real—but bounded by implementation maturity, not specification ambition.
10:34
Internet Message Access Protocol1986IMAP establishes email as a shared, persistent, server-managed resource—not a transient download. It works by defining precise commands for mailbox operations, flag persistence, partial message fetches, and extensibility—all over port 143. What works is its concurrency model, server-side search, and folder management. What does not is any guarantee of implementation fidelity, security defaults, or performance. It changes how email scales across devices and teams. It is worth your time if you rely on synchronised, searchable, cross-platform access to live mailboxes.
Up next in Technology

Package manager

· 9:37

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

Next brief →Back to Software
9:37