or go to full-text search page →

Search

Search IconIcon to open search

Plain Text Files

Last updatedUpdated: by Simon Späti · CreatedCreated: · 2 min read recently updated Recent changes 2 months ago +161 / −118 words 5 months ago +7 / −7 words 6 months ago +0 / −3 words 7 months ago +24 / −9 words 7 months ago +5 / −3 words 7 months ago +112 / −30 words

Knowhow stored in Notions and Google Docs will not scale (what if you need to change something?), we can’t do a search and replace. But why not use what developers have for ages for knowledge, too?

Plain text files are future-proof:

Every device, including ones long gone, and ones not invented yet, can read and edit plain text. Whether future virtual reality or a chip you can implant in your earlobe, plain text will be there. Will Microsoft Word? Evernote? Notion? Maybe. Maybe not.

Plain text files are:

  1. Portable
  2. Un-Commercial
  3. Offline
  4. No Dependencies
  5. Easiest to convert

# Markdown

This is the story of how Neovim/vim and Markdown unified my data engineering and writing workflow. As Kepano, the CEO of Obsidian says:

Obsidian will not exist forever, no app will. However, the files you create in Obsidian are yours, and can hopefully last for generations. File Over App

For me, Plain text files are the foundation, Markdown is the best plain text format there is, it’s is a text file still, but you have some formatting that are stored within the text, and Neovim and any other editor can open it in 100 years still. They will last until the end of days of computers. Read more at Markdown note.

# Relates

# Local First

Local First is an approach that heavily uses plain text files, and what Markdown and Obsidian for example use.

# Markup Languages

See more at Markup Language.

# Claude Skills

Arent’ Agentic Skills just Plain text files?

# Further Reads


Origin: