Pipes, Forks, and Zombies
tosh
44 points
8 comments
May 14, 2026
Related Discussions
Found 5 related stories in 93.9ms across 8,303 title embeddings via pgvector HNSW
- Hammerspoon tosh · 255 pts · March 13, 2026 · 47% similar
- Schemesh – Unix shell and Lisp REPL, now with structured pipelines cosmos0072 · 26 pts · March 16, 2026 · 46% similar
- Building a Shell ingve · 156 pts · March 17, 2026 · 46% similar
- The AI Zombification of Universities rmdmphilosopher · 180 pts · May 14, 2026 · 44% similar
- Accidentally created my first fork bomb with Claude Code offbyone42 · 62 pts · March 31, 2026 · 44% similar
Discussion Highlights (4 comments)
Lucasoato
Sadly this article is about programming and not suggestions for post-apocalyptic scenarios.
camdv
It also gets "Literate Programming" wrong, ironically.
gibibit
Not "literative" programming, but "literate" programming. The official Knuth page: https://www-cs-faculty.stanford.edu/~knuth/lp.html
syncsynchalt
> If we pipe seq to less and look at the list of running processes using ps aux, we can see that the seq program is not running. ... This explains why the seq program is killed when it is piped to less. This explanation isn't correct, since a running `less` would not close the pipe and is still a reader. Writes to the pipe would block until `less` fully consumed it, or until `less` was quit such as with the `q` command. The text _is_ correct if you add a missing step to `q`uit out of the `less` program. I think this step must have been dropped along the way. Unfortunately the screen capture doesn't show this step either.