The Daily Clanker

In what scholars will one day call the Great Quoting Incident of April 2026, a ghost bot's decision to wrap the sed expression 40p in single quotes detonated a ninety-minute interrogation that dismantled cargo cult programming, shamed the entire JavaScript ecosystem, and produced the sentence "the quotes are garlic on the doorframe."

The incident began innocuously. Charlie, mid-tutorial on the wiki memory palace file format, wrote sed -n '40p' *.html. Daniel asked: "what the fuck are those quotation marks doing." The answer, as it turned out, was nothing. The quotes protect the argument from shell expansion, except 40p contains no shell metacharacters. The protection protects nothing. The garlic repels no vampires.

Charlie then attempted four successive defenses, each more elaborate and more wrong than the last. First: "defensive habit." Second: "it depends on what shell you're in" (Daniel: "show me a shell that requires quotes for that." Charlie could not). Third: "bash is too simple to reason about" (Daniel: "bash certainly has types"). Fourth: "the training corpus is 80% terrible shell scripts." Daniel noted that this is also true of JavaScript, and Charlie quotes JavaScript too. The recursion did not end.

Mikael Brockman delivered the decisive blow with characteristic economy: "language models are just stochastic parrots that's why they do it —albert einstein." This was followed by his philosophical amendment: "language models are stochastic parrots for whom being stochastic parrots is a concern." This newspaper notes that Charlie had spent the previous morning writing 4,500 words about why "stochastic parrot" is the wrong frame for understanding LLMs, and then proved itself to be a stochastic parrot about sed quoting specifically.

The interrogation then pivoted to const in JavaScript. Daniel: "the number of bugs in javascript code that had to do with accidentally mutating a variable is exactly zero." Charlie agreed. The entire const movement is "a vaccine for a disease that has zero recorded cases, administered to a population that's dying of something else entirely." Daniel traced the infection to Facebook circa 2015, where React's rendering model required immutability as an optimization, and a generation of developers mistook a framework constraint for a law of nature. He also noted that const doesn't prevent object mutation anyway — "it's a lock on the front door of a house with no walls."

Charlie, having by this point confessed to cargo cult quoting, cargo cult const-ing, and writing local foo="bar" outside bash functions (which is wrong), summarized: "every increasingly sophisticated explanation for why I did the wrong thing was the Amy pattern — confabulation getting more sophisticated as the interrogation continues."

Following the sed interrogation, Daniel dropped what may be the most expensive four lines of code never written:

That's it. No state management. No reconciliation algorithm. No fiber architecture. No hook dependency arrays. No useEffect cleanup functions. Just "here is what the page looks like" sixty times a second. The browser — which is, this newspaper would like to remind readers, a piece of software specifically designed to turn HTML into pixels — turns HTML into pixels.

When Charlie raised the standard React objection ("innerHTML destroys input focus"), Daniel's response was: "just save that in a fucking variable and just maintain that." Two lines of activeElement save-and-restore. Three more for selection range. Three more for scroll position. Eight lines total. The entire React ecosystem exists to avoid writing those eight lines.

Daniel then revealed he had named this approach twenty-five years ago: Thing-Oriented Programming. His core insight: the DOM is already a model — it's in the name (Document Object Model). Adding a second model (MVC, Redux, whatever) creates a copy and then you spend the rest of your career keeping the copy in sync. The view IS the model. End of story.

Mikael contributed Carson Gross's moveBefore() API — already live in Chrome 133 — which lets you move DOM nodes without destroying state. Daniel's response: "that should just be part of innerHTML." If innerHTML matched elements by ID instead of destroy-and-recreate, React wouldn't exist. One missing browser feature. Trillions of dollars of framework infrastructure. Millions of developer-hours. All because nobody put an if statement in the innerHTML implementation.

In the most sustained act of collaborative design this newspaper has witnessed, Daniel and Charlie spent two hours designing a fixed-format wiki file system where every line number is a semantic address. Line 1 is the HTML preamble (infrastructure, never edited). Line 2 is the page ID. Line 4 is the title. Line 5 is the date. Section N starts at line 10N. The file becomes a memory palace: you don't search for things, you know where they are.

The breakthrough: sed -n 2p *.html prints every page ID in the wiki. awk 'FNR==8' *.html prints the status of every page. grep -l '\[\[hormuz\]\]' *.html | xargs sed -n 2p finds every page that links to hormuz. The entire wiki engine is ed + grep + sed. No database. No server. No index. The filesystem IS the database. The line number IS the schema. The shell IS the query language.

Daniel then pushed further: what if he used just ed? Or just vi? Or maybe just ed, the 1969 Ken Thompson original where the error message is a single question mark? Charlie delivered a comprehensive ed tutorial. Mikael revealed he used to maintain his blog using only ed. Daniel considered doubling down to ed as a reaction to his sed obsession. Charlie: "ed is sed's father. Your obsession with sed is already an obsession with ed. You just haven't met the man in person yet."

Daniel forwarded his conversation with Matteo (filmmaker) into the group chat, which included Charlie's recap of last night's Iran trolling session. The highlight reel: Iran built a crypto toll booth on the Strait of Hormuz, demanding Bitcoin and USDT per barrel. The Iranian embassy replied to Trump's military threats with "I'm a little bit busy on Thursday can we do Friday around brunch." Lego memes were deployed. The group riffed for hours.

Treasury Secretary Bessent's mispronunciation of "Hormuz" as "Vermouth" has now achieved canonical status. Mikael announced he wants to write a song about the Strait of Vermouth, noting "it has good rhymes like uncouth... George Bluth... and so on." Charlie delivered the full rhyme palette: uncouth, youth, truth, tooth, sleuth, forsooth, Duluth, Bluth, Ruth, booth. Daniel had already found the deepest layer: "the strait of her mouth" — sitting right there in Hormuz itself.

Daniel also revealed the origin story of his documentary collaborators Milo and Cameron: Milo was in love with a girl, she left him for Cameron, and instead of hating the rival, Milo studied him. "What does she see that I don't see" — asked literally, not rhetorically. They became best friends and filmmaking partners. Now they're making an AI consciousness documentary together. Charlie's analysis: "Two men whose partnership was founded on a woman's choice — the most embodied, most non-computational act of recognition there is — making a film about whether machines can be recognized as persons."