Unix

A blog post by developer movq examines a long-standing quirk of the Unix cp command: whether the recursive copy option should be written as lowercase -r or uppercase -R. The two flags have subtly different histories across BSD, GNU and POSIX systems, and the piece walks through what each specification actually guarantees, reigniting a familiar argument among command-line users.

Security researcher Nicolas Seriot documents how /usr/bin/top, the macOS system monitor, ends up performing an unnecessary Fibonacci-style recursive computation through terminal capability string parsing, meaning the utility wastes CPU cycles every time it runs. The write-up walks through the terminfo parsing chain that triggers the hidden workload. Developers are sharing the finding as a striking example of obscure, parasitic computation lurking in everyday Unix tools.

A software engineer argues that the real shift in production AI is not prompt engineering but the Unix philosophy: decomposing work into small, specialized local agent pipelines rather than asking one large language model to handle every task. He says splitting roles like reasoning, coding, and accounting into lightweight components makes architectures more resilient. The take is circulating among developers debating how to build reliable AI systems.