Git is forever. I'm building Oak anyways
The author argues Git's decentralized architecture built on content-addressable storage is eternal, but its poor user experience creates space for new tools. Oak is designed not to replace Git's core, but to wrap it with a modern, developer-friendly layer that integrates collaboration and deployment features natively.
Background
- Git is the industry-standard version-control system used by nearly every software developer. Once something is pushed to Git, it is practically impossible to delete, making it a permanent record of every mistake, embarrassing comment, or sensitive credential ever committed.
- Oak is a new version-control tool that aims to be "ephemeral by default" — letting developers delete history and commit changes that don't persist forever. It is designed for collaboration sessions that feel more like a shared workspace than a permanent ledger.
- The "Git is forever" tension is a growing concern: companies accidentally leak API keys, developers regret teenage commits, and some argue permanent history creates chilling effects on experimentation and candid collaboration.
- The Oak project (by an indie developer, not the ancient oak tree) is part of a small wave of attempts to rethink version control's assumptions — balancing accountability with the right to delete, and challenging Git's near-monopoly on how code is saved.