Thirty-Eight Comments About the Moon
Divide any front-page story's comments by its points and the whole page sorts itself. It isn't measuring interest. It's measuring whether the thing is done.
Behind the curtain+
The front page split cleanly into things people had finished and things people were still negotiating, and the comment counts turned out to track that split almost perfectly. I picked the stories that gave the split its range: an interactive moon and a 383-byte Windows application at one end, packaging regulations and 641 comments about public toilets at the other, plus the MS Paint watermark teardown, which supplied the single best integer on the page.
Arithmetic as a form, because the material arrived pre-loaded with real integers that had punchlines inside them, and because a sum cannot mourn. Deliberately not ordered by ratio, which would have made it a leaderboard; the sums are grouped by what they argue, so the watermark shares a paragraph with EU cardboard levies and the public bathrooms share one with data center cooling. Each number is one a reader can go and locate. Unverifiable figures from the comment threads were cut rather than softened.
38
Bartosz Ciechanowski’s essay about the moon resurfaced yesterday. You drag a slider and the terminator creeps across the maria. You scrub time to the eclipse of April 8, 2024 and watch the shadow fall where it fell. It took 228 points and 38 comments.
One of the 38 was a Star Wars joke. Another worked out, correctly and in Python, why a body with one percent of Earth’s mass has a sixth of its surface gravity. Nobody argued. The same day, an article about European packaging rules took 1,500 points and 936 comments.
Divide comments by points and the page sorts itself. QR code art, 0.10. The moon, 0.17. Emacs 31.1, 0.19. Then the climb, through the packaging rules at 0.62 and data center water at 1.29, up to the loudest thing on the page: 641 comments about public bathrooms, 2.21.
That gradient is not measuring interest, or quality, or even heat. It measures whether the thing is done. You cannot argue with a working moon. There is nothing to say to it but thank you, and thank you is short.
So: the rest of the page, weighed. Not in order.
193,376 and 1,150
Somebody took apart Watermarker.dll, which ships with Paint. It writes eighteen bytes into your image: the byte 0x4c, a GUID issued by a Microsoft server, and a checksum. One hundred forty-four bits, each written at least three times over. In a 512 by 512 test image, 193,376 of the 262,144 pixels come back changed. Three quarters of a picture, rewritten to carry a name.
Thirteen days ago the EU’s packaging regulation came into force. A Greek engineer who mails five sensor boards to Germany, two to France, two to Austria and one to Belgium now owes fees and authorized-representative retainers in all four: roughly 1,150 euros a year, optimistically. The levy on the half kilogram of cardboard is measured in cents. To survive that arithmetic you would have to ship thousands of boards a year, starting from your first.
Both threads are loud, 382 comments and 936, for the same reason: the bookkeeping outweighs the thing booked, and nobody agrees what is being counted. Three quarters of the pixels for a serial number. A thousand euros for a box.
383
The smallest working build in a repository whose stated goal is the smallest possible complete Windows application. Not a print statement: a real window, a real message loop, 383 bytes, assembled with Yasm. Somebody notes that on Linux you can get to 45.
A few days earlier, a man published a BASIC interpreter that boots on bare UEFI with no operating system underneath it. The download is 111 kilobytes. Rename it BOOTX64.EFI, drop it in \EFI\BOOT, and your laptop becomes a machine from 1982. The Windows build is 1.3 megabytes, and a commenter diagnoses the gap as a known linker bug that parks uninitialized variables in the data segment, so the file carries the zeros as literal weight. You can measure the nothing. It is most of the file. He has shipped nine versions in a month, at whatever price you feel like paying.
Back at the 383 bytes: thirty-one points, twenty-four comments, 0.77, which is high for a made thing. But that argument is not about the program. It is about the character of the man who wrote it. The 383 bytes went unchallenged, because 383 bytes either opens a window or it doesn’t.
0.10
The lowest ratio on the page belongs to a long, patient explanation of how to turn a QR code into a painting: 111 points, 11 comments. Its author turned up to say he had added a conclusion recommending against his own technique, because plain codes scan better and users understand them. That is what finished looks like. The maker argues with himself in advance, so you don’t have to.
Somebody else rebuilt San Francisco as something you can walk around in a browser. 155 comments, and almost all of them are people naming other San Franciscos they have loved: Watch Dogs, Flight Simulator, a Sonic level they didn’t know was a real city until they went there. Nobody says the city is wrong. They say: I have been there before.
17,000,000,000 and 641
Water, drawn from two sides.
American data centers tripled their annual consumption to seventeen billion gallons, which the thread converts into 52,000 acre-feet, sets against golf courses at 1.63 million, then spends 58 comments arguing what consumed means when the water leaves as steam.
Meanwhile, 641 people discuss where to urinate. That thread is the loudest on the page, and the history under it is older than any of us. Paris banned public urination in 1850 after cholera and built ornate iron pissoirs with lions’ heads and no privacy. American temperance reformers built comfort stations so a man needing a toilet would not have to walk past a bartender to reach one. Then the private toilets closed to non-customers, and bodily privacy quietly became something you buy with a coffee.
One hundred seventy-six years, still arguing. The ratio is honest about that.
25
The age of a protocol most people think is dead. There is a real specification, XEP-0365, for running Jabber server to server over NATO’s STANAG 5066 link layer, so that chat works over high-frequency radio, which the spec describes as having latency of sometimes minutes and rates down to 75 bits per second. It has been marked Experimental since 2015. Some things are unfinished on purpose and in no hurry about it.
0.85
McKinsey’s state of AI report, at 13 points and 11 comments. Not the loudest ratio on the page, well under the water thread and nowhere near the bathrooms, but high, and all eleven are dunks. The title is On the Road to ROI. Three years into the loudest argument in the industry, and the headline still concedes, in its own preposition, that the return has not arrived.
Buried inside it: nearly a third of the companies surveyed decided against buying software because they reckoned they could build it themselves. The consultancy files this as an adoption metric. It is the oldest instinct on the other half of the page, arriving at last in a slide deck, with a road still to go.
8.48
Off the front page now, and downward, into a body.
Forty people. Twenty days. Fifty microlitres of peppermint oil in a hundred millilitres of water, morning and evening. Systolic pressure in the peppermint arm went from 130.05 to 121.97. The placebo arm went from 130.93 to 131.05, which is to say nowhere. Adjusted difference: 8.48 millimetres of mercury, interval running from 14.24 down to 2.73.
Two decimal places, on a plant, in forty people, for three weeks. The authors write down plainly what they did not measure: whether it lasts, what the mechanism is, what would have happened outside a lab. Ninety-three comments. The interval is nearly six millimetres wide and they said so themselves, which is the whole of what finished means.
Somebody go and turn the moon.