06 This domain
Why the name stays
The tool is gone. The condition it named is everywhere.
The problem is the right noun
Slowy was a small Mac utility that deliberately degraded a network connection — adding latency, dropping packets, capping throughput — so that developers could watch their software fail gracefully, or not. It ran on a specific version of a specific operating system and at some point stopped working, as tools built close to a kernel tend to do. The software has a past tense. The name does not.
What the name points at is not an application. It is a condition: the link that cannot keep up, the queue that has grown too long, the connection that works but barely. "Slowy" is not a technical term, and that is precisely its utility. It names the experience before the mechanism — the spinning cursor, the dropped call, the video that smears into blocks — and that experience has not gone anywhere. If anything, it has become more consequential as more of daily life depends on a network path behaving predictably.
The technical literature has its own vocabulary for this. Van Jacobson's 1988 paper on congestion avoidance and control, written at Lawrence Berkeley National Laboratory in Berkeley, California, described what happens when a network fills up and senders do not back off: queues grow, latency spikes, throughput collapses. Jim Gettys gave the sustained version of that collapse a name — bufferbloat — and the community that formed around Bufferbloat.net spent years quantifying it, building active queue management algorithms such as CoDel (designed by Kathleen Nichols and Van Jacobson) to fight it. The vocabulary is precise and earned.
But precise vocabulary is for engineers diagnosing a cause. "Slowy" is for anyone who needs to reproduce a condition — the bad hotel Wi-Fi, the satellite uplink on a cargo ship, the mobile handoff that takes three seconds to settle — and make software behave inside it. The name is a description of what you are trying to simulate, not what you are trying to understand, and that distinction keeps it useful long after the original binary became inert.
Names outlast tools all the time when the names point at something real. Dummynet, Luigi Rizzo's shaping engine built at the University of Pisa, is still the machinery inside several modern packet filters; the name has survived every kernel revision around it. The condition a name describes is more durable than any implementation.
This guide exists because the problem Slowy was built to surface — software that has never genuinely faced a bad connection — has not been solved. The name stays because the problem stays, and a name that tells you immediately what you are dealing with is too useful to retire.
