The Fragility of the Digital Dark Age
The digital world is littered with the corpses of ‘revolutionary’ file formats. If you have a floppy disk from 1992 containing a WordStar document or a proprietary database file from a defunct 1990s accounting suite, you don’t own data; you own a digital fossil. Modern software treats your information like a temporary guest, but plain text longevity offers the only real guarantee that your thoughts will survive the next two decades. We are currently living through a period of extreme digital fragility where the average lifespan of a Silicon Valley startup is significantly shorter than the time it takes to raise a child. If you store your life’s work in a proprietary format, you are betting that a specific company will stay profitable, maintain its servers, and keep its pricing model compatible with your budget forever. History suggests that is a losing bet.
Plain text is the bedrock of computing. It is the closest thing we have to a universal language for machines. While file formats for word processors, spreadsheets, and databases have come and gone, the humble .txt file has remained unchanged in its core utility. This permanence is not an accident; it is the result of simplicity and a lack of hidden complexity. When you strip away the layers of styling, metadata, and proprietary code, you are left with something that any computer built in the last forty years can understand. It is the difference between a stone tablet and a encrypted tablet computer with a proprietary charging port. One requires a specific environment to function; the other simply exists.
The Lindy Effect and Digital Endurance
The Lindy Effect suggests that the future life expectancy of a non-perishable thing, like a technology or an idea, is proportional to its current age. If a book has been in print for fifty years, it is likely to be in print for another fifty. If a software startup has been around for three years, it is statistically unlikely to survive another ten. Plain text has been the standard for digital communication since the inception of the internet. Because it has survived every major architectural shift in computing—from mainframes to desktops to mobile and the cloud—it is the most likely format to survive the next several.
Compare this to the current landscape of productivity apps. Most modern note-taking tools store your data in a database hidden behind a proprietary interface. You do not own a file; you own a login. If that company decides to pivot, gets acquired by a larger firm that guts the product, or simply goes bankrupt, your data becomes a liability. We saw this with the decline of Evernote, where a once-dominant platform became bloated and expensive, leaving users scrambling to migrate thousands of notes. You might be able to export it, but the export is often a messy collection of JSON or HTML that loses the structure and connections you spent years building. Choosing a format based on plain text longevity means you are opting out of this cycle of planned obsolescence. You are moving from a system of permission to a system of ownership.
The Technical Foundations of Plain Text Longevity
The reason plain text scales across decades is its adherence to open standards. Unlike a .docx or a .pages file, which requires complex software to parse and render, plain text is transparent. Every byte corresponds to a character. This transparency means that even if every specialized note-taking app disappeared tomorrow, you could still open your files in a basic system terminal. Standardization like UTF-8 ensures that character encoding remains consistent across different cultures and languages. This level of compatibility is why developers use plain text for the world’s most critical infrastructure: source code. If the code that runs our banks, power grids, and spaceships is stored in plain text, it stands to reason that your personal knowledge base should be as well.
Furthermore, plain text is lightweight. A thousand notes in plain text take up less space than a single high-resolution photograph. This makes backups trivial. You can mirror your entire knowledge base across multiple hard drives, cloud providers, and physical locations in seconds. You are not at the mercy of a sync engine that might fail or a server that might go offline. You have total control over the redundancy of your information. In the 1960s, ASCII was established as a 7-bit character set. Today, those files are still readable. Can you say the same for a file created in a proprietary ‘knowledge graph’ app from 2021?
Escaping the Cathedral of Proprietary Formats
Proprietary formats are often referred to as ‘walled gardens,’ but they are more like cathedrals where the architect holds the only key. When you enter, you agree to their rules and their vision of how information should be organized. This works well until the architect decides to change the layout or close the doors entirely. We have seen this happen with platforms like Google Reader or Microsoft Encarta. Users who spent years meticulously organizing their lives in those systems were forced to migrate, often losing data or formatting in the process. Migration is the hidden cost of proprietary software. Every time you move from one tool to another, there is a tax on your time and your data integrity. Links break, attachments go missing, and the mental model you built is shattered.
By prioritizing plain text longevity, you eliminate the need for massive migrations. You might change the application you use to view and edit your files, but the files themselves stay exactly where they are. They remain on your hard drive, in your folder structure, under your names. This is the ‘File-over-App’ philosophy. It posits that the data is the primary asset, and the software is merely a temporary lens through which you view it. If the lens cracks, you find a new one. You don’t lose the view.
Why Markdown is the Bridge to the Future
Plain text is durable, but it lacks the structural features needed for complex note-taking, such as bolding, headers, and links. This is where Markdown becomes essential. Created by John Gruber in 2004, Markdown is a syntax that adds structure to plain text without compromising its longevity. It is human-readable even in its raw form. If you see a word surrounded by double asterisks, you know it is bold. If you see a bracketed word followed by a URL in parentheses, you know it is a link. Markdown provides the ‘Goldilocks’ solution for long-term digital storage. It offers enough features to support a sophisticated second brain—including tables, task lists, and math symbols—while remaining entirely plain text.
Because Markdown has become the de facto standard for technical documentation and web content, the ecosystem of tools supporting it is massive. If one Markdown editor stops being updated, there are dozens of others ready to take its place immediately. This interoperability is the key to a sustainable knowledge practice. You can use one app for mobile editing, another for desktop deep-work, and a third for publishing to the web, all while pointing at the same set of files. This workflow is only possible because the underlying data is not trapped in a database. It is just a folder of files. This approach allows your system to grow and evolve with you, rather than being limited by the feature set of a single piece of software.
Building a Legacy with Local-First Principles
To truly benefit from plain text, you must adopt a local-first mindset. This means your primary copy of your data lives on your machine, not on a remote server. The cloud should be used as a transport layer or a backup, not as the source of truth. When your notes are local, they are fast, they work offline, and they are private by default. You are no longer vulnerable to internet outages or data breaches on a company’s server. Local-first software treats your files with respect. It doesn’t hide them in obscure library folders or rename them with random strings of numbers. It lets you see them in your file explorer.