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 "CLOSURE".
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:
5. yes, this was a puzzle of sorts, though the answers were kind of given to us beforehand, so you can argue that it wasn't a difficult puzzle. The PDF is the "answer" to the puzzle, if you will.
I'm 48. I don't think age has anything to do with knowing the context behind this. From the other explanations, you apparently had to follow a very specific subculture dedicated to a specific individual. I did not, rather the opposite. I tried to read his Ruby book when it came out and I simply couldn't. No offense to the vast army of folks who enjoyed it -- I think we're all allowed to like what we like.
There's something wrong with the way my brain is wired. I am by accounts an intelligent, capable, successful person, but I am completely unable to "read" comic books. I might as well be staring at a foreign language. When I'm trying to learn a technical topic, I thrive on dry reference material. Put a cartoon in and it's like running into a brick wall.
I don't know where I was going there except I feel like any time this comes up, I have to over-explain myself for not liking that book, because everybody loves that book and I will be burned at the stake for not regarding it as the greatest programming book ever written. It's just my personal experience, and I accept that I'm totally wrong about it, ok? Anyway, shorter version is that I had such a visceral reaction, any time I see "why_" mentioned, my reading comprehension reverts to that of a toddler.
If that's all irrelevant and the point you were making was more like "kids today don't know what PCL is", I am very familiar with PCL and print spoolers, but detached from any context that would suggest printers, they failed to take on any semantic value.
Idem. I remember not being able to get past the first page of the guide way back in the day, and indeed cannot today either. The signal to noise ratio is just abysmal.
I also cannot read comic books and, with perhaps the exception of the systemd man pages, likewise thrive on reference material.
Somewhat relatedly, I can't really do podcasts or audiobooks, either, unless they're in a foreign language, and then the challenge of comprehension provides something for my brain to latch onto.
You can be perfectly capable of reading a comic book and not really care to try to learn technical information by way of a comic book.
I'd much rather learn from concise code examples, with short explanations for new concepts. It's a lot more efficient than wading through all the irrelevant prose and illustration.
Printer Common Language. More an alternative to PostScript than to PDF, in that it's a language that a lot of printers understand (as the name suggests).
No, it's HP Printer Command Language[1]; it's the 'native tongue' of things like HP LaserJets. It predates and is different from PS and PDF[2] and isn't an alternative for PDF in that you don't store documents 'in PCL'.
