De-Rusted Git Fork: 'Git with WD-40 Applied' — Meme Explained

Level 1: The Clubhouse Rulebook

A group of friends has been building a treehouse with hammers and nails for twenty years. One day the leaders announce that from now on, everyone must also own a fancy new power tool — it's safer and most people already have one. One kid gets so annoyed that he photocopies the entire treehouse blueprint, erases every mention of the power tool, and starts his own treehouse next door with a sign that says "Now with rust remover!" It's funny because the new tool is literally called Rust, the spray that removes rust is a garage classic, and storming off to build your own copy is somehow both a tantrum and completely allowed by the clubhouse rules.

Level 2: Glossary for the Flame War

• Fork: copying a project's source to develop it independently. Forks range from "weekend experiment" to "OpenOffice → LibreOffice, the original dies." The right to fork is the core freedom of open source.
• Rust: a systems programming language whose compiler statically prevents most memory-corruption bugs (buffer overflows, use-after-free) that haunt C codebases. Beloved, evangelized, and resented in roughly equal measure.
• Hard requirement: a dependency you cannot build without. Today Git builds with a C compiler — present on effectively every platform since the 1980s. Requiring Rust narrows that to platforms LLVM supports.
• Toolchain: the full stack of compilers and build tools needed to produce a working binary. Adding a language doubles the toolchain surface.
• XLibre: a contentious fork of the X11 display server, itself born from a governance dispute — making its developer a serial protest-forker.

The early-career lesson: language adoption decisions in infrastructure projects are never purely technical. They're about who can contribute, who can build, who gets left behind, and whose decades of expertise just got devalued. The code compiles either way; the community sometimes doesn't.

Level 3: The Fork Heard Round the Mailing List

The headline reads like satire and is, delightfully, journalism: "XLibre Dev Creates de-Rusted Git Fork — As Git prepares to make Rust a hard requirement for Git 3.0, this fork removes all Rust code and describes itself as 'Git with WD-40 applied'." Every layer of this is a chapter in the ongoing Rust culture war, the most reliable source of open-source drama since the systemd flame wars and the vim/emacs holy wars before it.

The background: the Git project — like the Linux kernel before it — began admitting Rust into a codebase that has been pure C since Linus wrote the first version in a caffeinated weekend in 2005. Making Rust a hard toolchain requirement for Git 3.0 is the line-in-the-sand moment: it means you can no longer build Git on any platform that lacks a Rust compiler. For mainstream platforms, irrelevant. For maintainers of obscure architectures, retro-Unix ports, and minimal bootstrap environments, it's an eviction notice. This exact argument played out in the kernel with enough heat to burn out several maintainers on both sides — memory safety and modern tooling versus toolchain portability, build-chain complexity, and the social friction of telling twenty-year C veterans to learn lifetimes.

The forker's pedigree completes the picture. XLibre is the protest fork of the X.org display server, created by a developer at odds with what he considers the freedesktop establishment's stewardship (and its drift toward Wayland). Protest-forking is the open-source equivalent of constitutional law: the right that legitimizes everything else. Usually the fork withers — maintaining a divergent copy of an actively developed project is a treadmill that accelerates forever, and ripping Rust out of Git means re-implementing or freezing every future feature the upstream writes in Rust. But the fork's existence is the argument: "your hard requirement isn't hard for me."

And then there's the name. "Git with WD-40 applied" is genuinely elite wordplay — WD-40 is the rust remover in every garage, so "de-Rusting" a codebase with it makes the pun operate at the literal, chemical, and programming-language levels simultaneously. The fact that WD-40 is technically a water displacer that mechanics will tell you is not a proper long-term lubricant — a temporary fix that feels great and solves nothing permanent — may be the most accurate part of the metaphor, intentional or not.