HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
steveklabnik
CLOSURE
OPEN SOURCE2015–2025
steveklabnik / CLOSURE

CLOSURE

Thanks, _why.

10Distinct people
11Mentions
0Explicit recommenders
546GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Thanks, _why.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year11 dated mentions

Observed mentions: 2015-07-16 17:22:54 UTC to 2025-08-12 14:05:56 UTC.

01232015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC110
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC110
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC312
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

11 sources
A few weeks/months before _why published this book, this page appeared on his "public print queue" on his site, hinting that the print queue would become active on April 18: https://github.com/steveklabnik/CLOSURE/blob/master/PDF/DESO... A day or two before April 18, this page appeared containing a hand-written OCaml script you could use to hook up your own printer to _why's public print queue: https://github.com/steveklabnik/CLOSURE/blob/master/PDF/HOME... On April 18, a bunch of us gathered in an IRC chat room (https://viewsourcecode.org/why/CLOSURE/ircLog.html). A few of us got the script working on our machines, and so every 10-15 minutes our printers would suddenly start up and print the next page as _why slowly published them one at a time throughout the day. Steve Klabnik gathered all the pages into one PDF and gave it the name "CL
Read the rest
OSURE". This article does a good job of giving more context around the book itself (as well as a partial summary): https://kev.town/2013/04/30/why-did-why-the-lucky-stiff-quit...
In Closure, from why the lucky stiff (2013)
From: https://github.com/steveklabnik/CLOSURE/issues/3 -- vi commented on Sep 30, 2015 What is CLOSURE.PDF? Readme is not helpful. I don't even understand is it a scientific paper, a book, a program or a game. My first thought was "Fed up! I'm closing! Here is my closure manifesto." Along with Thanks, _why. there should be answer to What is CLOSURE? question in repository description. -- mikehenrty commented on Aug 13, 2016 I think the problem is that nobody except for _why and perhaps a few people close to him know the context of this material. It just showed up on his blog one day after years of online radio silence. These hacker news posts show some of the confusion and excitement from that time: https://news.ycombinator.com/item?id=5015087 https://news.ycombinator.com/item?id=5571387 Note that the link from Hacker News, _why's origina
Read the rest
l blog, is now operated by some Australian guy with no apparent relation to _why.
In Closure, from why the lucky stiff (2013)
It is assumed but not proven that _why's final thoughts about killing that pseudonym are captured in CLOSURE [1]. There's a lot of different takeaways from that and other contemporary writings of _why. Some of them are that _why wished to pursue the Right to Be Forgotten, not just in the GDPR terminology sense, but in a "Last Chance to See" existential way. Those impressions yield that _why watched the internet transition from "pseudonyms are fine and ephemeral" to "everyone knows your real name and pseudonyms are permanent fixtures in the modern internet" and tried as hard as possible to kill everything about that pseudonym as Performance Art. As a reminder of an internet long gone. As a reminder of a Right to be Forgotten. From that perspective, this archive is maybe a bit of putting a Banksy into the Louvre. It's out of context, it's m
Read the rest
aybe against the artist's wishes, it's kind of weird and over-pedestalizing a legendary figure. (Arguably _why's last stand failed to account for that little last bit, that human tendency even older than the internet of myth making and legend building. As this shows, as the history of mentions of _why on HN alone every few months shows, legends loom large in culture and _why was already a part of the programming legendarium before he tried to murder that pseudonym.) [1] https://github.com/steveklabnik/CLOSURE/raw/master/CLOSURE.p...
In Whytheluckystiff's original domain back as an archive
As far as I understand, he quit his public life when someone hunted down and published his real name and address. He removed his website and github, which contained his various writings, some of which had names with "tutorial" or "guide" in them but all of which were at least 80% works of literature and at most 20% works of technical documentation. Not sure I would call it "ragequitting". Virtually all his works were archived by fans and can be read for example here: https://viewsourcecode.org/why/ A few years ago he published a sort of absurdist goodbye (as a live-updating printer spool) which Steve Klabnik collected into a 95-page PDF here: https://github.com/steveklabnik/CLOSURE His blog contained many small snippets of code that were definitely meant to be consumed as poetry, they are easy to spot because of all the colors and shapes
Read the rest
and sometimes animations: https://viewsourcecode.org/why/redhanded/ But my own experience of learning from him how to experience code as poetry mostly involved around using Camping in production for some small side projects and needing to explore some bits of its code because of practical reasons: https://github.com/camping/camping
In Weird-Looking Freak Saves Apollo 14 (1971)
I'm sure you know much of this, but essentially: - August 2009, he died. (i.e. removed his entire estate and entity from the web after being doxxed) - He reappeared for one day in 2013, to release a 100 page document on a briefly live printer queue called "CLOSURE" (and a few other potentially unrelated posts such as youtube videos), which can be found here: https://github.com/steveklabnik/CLOSURE - His estate, preserved as much as it can be, is here: https://viewsourcecode.org/why/ - A few months after CLOSURE was released, Steve Klabnik gave a talk on it https://www.youtube.com/watch?v=MaWHVceDbFo
In _why's interview with DHH was 15 years ago this week

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.