The thirty-year argument ended in a driver directory

The remarkable thing about the kernel's Rust decision, covered in last week's dispatch, is not that it happened but how quietly the ending arrived. No summit, no vote, no manifesto. A label came off in a changelog. Three decades of "C is the only language fit for this work" concluded as a line item.

Big technical arguments tend to end this way, and the pattern is worth naming because organizations keep expecting the other kind of ending. They stage the debate, commission the bake-off, wait for the decisive meeting where the question is settled. The kernel's question was not settled in a meeting. It was settled by a few years of drivers that worked, submitted by people who kept showing up, reviewed under rules that kept getting refined, until the day the experimental label described nothing true anymore.

The rhetoric mattered less than the procedure. What the Rust effort actually won was administrative: a build system that tolerated it, maintainers willing to review it, a subsystem where failure would be survivable. Arguments are won by whoever makes their preferred future the path of least resistance, and then waits.

The builder's read: if you are championing a technology change, stop scheduling debates. Ship the contained version, make it boring, and let the label fall off when nobody can remember why it was there. The argument you win rhetorically reopens next quarter. The one you win administratively is just how things work now.