"When you say "I wrote a program that crashed Windows," people just stare at you blankly and say "Hey, I got those with the system, for free.""
About this Quote
A wry jab from Linus Torvalds captures a moment when Windows crashes were so common that causing one was no accomplishment. The punchline lands because it flips the expected brag of a programmer on its head: what sounds like technical prowess earns only a shrug, since instability already came bundled with the dominant operating system.
The context is the late 1990s and early 2000s, when consumer versions of Windows (notably 95 and 98) were infamous for the Blue Screen of Death. Architectural choices, such as weaker memory protection and drivers running with high privileges, made it easy for a single misbehaving application to bring down the whole machine. Users learned to accept reboots and data loss as part of daily life. Against that backdrop, claiming to crash Windows was like boasting you could make water wet.
Torvalds’ quip also plays with the language of “free.” Consumers had paid for Windows, but the defects felt included at no extra charge. For a figure aligned with free software ideals, the irony is deliberate: free-as-in-crashes is not the kind of free anyone wants. The line becomes a critique of market dynamics that reward convenience and ubiquity over reliability, and of a culture that normalizes poor quality because everyone shares the pain.
There is a deeper shift implied about operating system design and expectations. Unix-like systems, including Linux, aim to isolate processes so one failure does not topple the system. They are not flawless, but the philosophy values containment, transparency, and fixability. The humor underscores the open-source movement’s challenge to proprietary opacity: if users and developers can see and repair the problems, they do not have to live with them.
Ultimately the joke calls attention to lowered standards. When crashes are expected, excellence looks unnecessary. The barb invites both users and developers to demand more than what arrives “for free.”
The context is the late 1990s and early 2000s, when consumer versions of Windows (notably 95 and 98) were infamous for the Blue Screen of Death. Architectural choices, such as weaker memory protection and drivers running with high privileges, made it easy for a single misbehaving application to bring down the whole machine. Users learned to accept reboots and data loss as part of daily life. Against that backdrop, claiming to crash Windows was like boasting you could make water wet.
Torvalds’ quip also plays with the language of “free.” Consumers had paid for Windows, but the defects felt included at no extra charge. For a figure aligned with free software ideals, the irony is deliberate: free-as-in-crashes is not the kind of free anyone wants. The line becomes a critique of market dynamics that reward convenience and ubiquity over reliability, and of a culture that normalizes poor quality because everyone shares the pain.
There is a deeper shift implied about operating system design and expectations. Unix-like systems, including Linux, aim to isolate processes so one failure does not topple the system. They are not flawless, but the philosophy values containment, transparency, and fixability. The humor underscores the open-source movement’s challenge to proprietary opacity: if users and developers can see and repair the problems, they do not have to live with them.
Ultimately the joke calls attention to lowered standards. When crashes are expected, excellence looks unnecessary. The barb invites both users and developers to demand more than what arrives “for free.”
Quote Details
| Topic | Coding & Programming |
|---|
More Quotes by Linus
Add to List
