Version Control Is Having a Moment. Your Notes Deserve a History You Own.

Version control is the most boring corner of software, and in 2026 it became the most interesting. Jujutsu, a calmer alternative to Git, has climbed to nearly 30,000 GitHub stars and grown into a full-time project at Google.¹² A newer system, Lore, hit the front page of Hacker News with over 1,200 points.³ The renewed attention is not really about tools. It is about owning a complete history of your work — which is exactly the thing your notes are missing.

Developers spend their careers building one quiet asset that travels with them: a full, local, owned record of every change they have ever made. The current wave of version-control tools is a fresh argument for why that record matters. The argument transfers cleanly to writing. Your notes, your research, the half-formed paragraphs you will need again in a year — those have a history too, and in most note apps you do not own it.

Why is version control suddenly trending again in 2026?

Version control is trending because a generation of tools is fixing the part everyone hated: the ceremony. Jujutsu (its command is jj) sits on top of Git's storage but replaces Git's awkward workflow with a quieter one. It removes the staging area, treats your working copy as a commit that updates itself, and lets you undo almost anything. The result feels less like operating a machine and more like writing.

The momentum is real and multi-year, not a single spike. Jujutsu describes itself as "a Git-compatible VCS that is both simple and powerful," and its creator, Martin von Zweigbergk, writes in the project's README that he "started Jujutsu as a hobby project in late 2019, and it has evolved into my full-time project at Google, with several other Googlers (now) assisting development."² Threads about it have repeatedly reached the Hacker News front page across 2022 through 2026. In June 2026, an unrelated system, Lore, joined the wave at 1,241 points.³ When the most ignored layer of software starts trending, something underneath has shifted.

What makes Jujutsu calmer than Git?

Jujutsu is calmer because it removes the three places Git most often trips people: the staging area, the commit ritual, and blocked merges. The README states plainly that "There is no explicit index or staging area."² Changes are "recorded automatically as normal commits, and amended on every subsequent change."² You stop managing snapshots; the tool keeps the history for you.

The deeper change is in how the two systems treat mistakes and conflicts. Git, by design, "does a simple three-way merge, using the two snapshots pointed to by the branch tips and the common ancestor of the two," and a conflict stops you until you resolve it.⁴ Jujutsu records the conflict and keeps going.

Two honest notes. Jujutsu is young — a hobby project that began in late 2019 — and it sits on Git rather than replacing it; treat it as a friendlier front end over Git's storage, not a revolution. And its design claims come from the project's own documentation, which is the right primary source for what a tool does, but it is the maker's account, not an independent audit.

Is Jujutsu really "used by Google"?

Jujutsu is genuinely developed at Google, but the precise, defensible claim is narrower than the hype. Its creator describes it in the README as having "evolved into my full-time project at Google, with several other Googlers (now) assisting development."² That is a credible signal: a major engineering organization staffs people to work on it. It is not a corporate endorsement, a guarantee, or proof that it is the "most production-validated" anything.

The honest read is that Jujutsu has serious institutional backing and a fast-rising community, which is why it keeps surfacing in 2026. Even an enthusiastic practitioner stays measured about it. Steve Klabnik, who wrote a popular tutorial for it, opens by saying "I am very excited about jj. I feel like I'm getting it," and immediately adds, "I make no claim that this tutorial is good, complete, or even accurate."⁶ That mix — real excitement, no overclaiming — is the right posture for a young tool, and a useful posture to borrow before you adopt anything.

What does any of this have to do with my notes?

It has everything to do with your notes, because the whole point of version control is the thing your notes usually lack: an owned, complete, recoverable history. Git's design lesson, stated in its own book, is that "Because you have the entire history of the project right there on your local disk, most operations seem almost instantaneous."⁵ The history lives with you. It is not rented from a server.

Now apply that to your writing. Most note apps store your words in a proprietary store you cannot diff, cannot roll back to last Tuesday, and cannot fully extract when the company changes direction. You can see the current state of a note. You cannot walk its past. The version-control wave is developers rediscovering, loudly, that a history you own is worth building — and notes are the one part of your intellectual life where almost nobody has one.

The fix is not a developer tool. It is a format. Plain-text Markdown files, stored locally on your own device, can sit under any version system — a developer's tool, a simple snapshot utility, or just dated copies in a folder. Because the notes are files you control, the history is yours: diffable, recoverable, and able to outlive any single app. This is the local-first ideal that Ink & Switch named the "Long Now," where "your work should continue to be accessible indefinitely, even after the company that produced the software is gone."⁷

Do I need Git or Jujutsu to version my notes?

No. Most people do not need Git, Jujutsu, or any developer tool to keep a history of their notes — and you should not start there. Dated copies in a folder, a snapshot tool that runs on a timer, or a notes app with built-in history will all do the job. The point is owning the history, not adopting a command-line program built for software teams.

What matters is the substrate underneath. If your notes are plain files you control, every option above is available to you, and you can change your mind later without migrating anything. If they are locked in an app's private store, none of them are, and the app owns your past. Steph Ango, who leads Obsidian, put the principle in one line: "Apps are ephemeral, but your files have a chance to last."⁸ He calls it file over app — "a philosophy: if you want to create digital artifacts that last, they must be files you can control, in formats that are easy to retrieve and read."⁸ Version control is that philosophy, formalized and made automatic.

For the concrete how-to — initializing a simple version history for a notes folder, browsing it, and recovering an old draft — see our companion piece on keeping a version history for notes you own. And keep three ideas separate: a version history lets you go back; a backup protects against loss; an export lets you leave. They are related, but they are not the same thing.

FAQ

What is Jujutsu and why is version control trending again? Jujutsu (jj) is "a Git-compatible VCS that is both simple and powerful" — a version-control system that uses Git for storage but offers a calmer workflow.² Version control is trending in 2026 because tools like Jujutsu remove Git's friction, drawing nearly 30,000 GitHub stars¹ while newer systems like Lore top Hacker News.³

What is the difference between jj the CLI and Jujutsu? They are the same project. Jujutsu is the version-control system; jj is the command-line program you run to use it. The README describes it as "compatible with many of your favorite Git-based tools, right now."²

Is Jujutsu used internally at Google? Its creator states in the README that Jujutsu "has evolved into my full-time project at Google, with several other Googlers (now) assisting development."² That is genuine institutional backing, not a corporate endorsement or a claim that it is the most production-tested Git alternative.

Do I need Git or Jujutsu to version my notes? No. Dated copies, a snapshot tool, or a notes app with built-in history are enough for most people. The goal is owning a recoverable history, not adopting a developer tool. The requirement is that your notes are plain files you control.

How is a version history different from a backup? A version history lets you return to any past state of your work, change by change. A backup protects a copy against loss or device failure. You can have a backup with no usable history, and a history you have never backed up — keep both, and do not confuse one for the other.⁵

Why does file format matter for keeping a history of my notes? Because a history is only as durable as the files it tracks. Plain-text Markdown is readable by countless tools and survives any one app, which is why Steph Ango argues that lasting artifacts "must be files you can control, in formats that are easy to retrieve and read."⁸

The renewed obsession with version control is, underneath the tooling, an old idea getting louder: a history you own is worth keeping. Developers have always had one. Your notes can have one too — if they are files you control, not entries in an app you rent.

For notes that stay plain files on your own device — open Markdown you can version, diff, and recover — see mnmnote.com.