The Long Road to “Just Text”
For many years now I’ve kept digital notes.
And for most of those years, I’ve had the same quiet frustration:
there must be a better way to manage all of this.
Not more features. Not more AI.
Just something more flexible. More mine.
The Illusion of the Tool
Around 2010, I started using Evernote.
At the time, it felt like magic.
- Desktop and web apps
- Seamless syncing
- Notes available everywhere
- Fast, reliable, polished
I even paid for it.
And for a while, it genuinely improved how I worked.
But slowly, something became clear:
The value wasn’t in the software.
The value was in my notes.
Evernote didn’t create anything for me.
It just made my own thoughts more accessible.
And once I saw that, it was hard to unsee.
Because if that’s true…
then what am I really paying for?
At some point, a simple idea took hold:
I could probably get most of this from a folder of text files
and a decent editor.
Back to Simplicity
That realization pulled me in a different direction.
I started spending more time in the terminal.
There’s something grounding about the CLI:
- no distractions
- no hidden layers
- no ambiguity
You always know where you are.
I explored Linux more deeply.
I used tools like vim, nano, and other terminal editors.
It felt… honest.
But still, something was missing.
The Emacs Moment
Then I discovered Emacs.
And for a while, I thought:
This is it. This is the answer.
The power was unbelievable.
- Fully programmable
- Deeply customizable
- Keyboard-driven everything
- Org-mode for tasks, notes, calendars, planning
No mouse. No friction. Total control.
And the most surprising part?
This problem had already been solved… in the 1980s.
I spent weeks configuring it.
Tweaking keybindings.
Learning bits of Lisp.
Building what felt like a personal operating system for my life.
It was incredible.
The Reality Check
But then reality set in.
I still love Emacs.
But…
It’s just too complicated.
Every time I come back to it, there’s a ramp-up cost:
- forgotten keybindings
- obscure commands
- config drift
- “how did I set this up again?”
It’s powerful—but fragile.
And beyond that:
- It’s not designed for multiple devices
- It’s not built for mobile
- Syncing feels bolted on, not native
It started to feel less like a tool I could live in
and more like a system I had to constantly maintain.
The Missing Piece
That’s when the real gap became obvious.
There wasn’t a single tool missing.
There was an entire ecosystem missing.
What I actually wanted was something like this:
- Seamless sync across devices
- Works offline and online
- Multiple storage options (local, cloud, decentralized)
- Multiple interfaces (CLI, desktop, mobile, web)
- Modular, extensible, adaptable
But most importantly:
No proprietary formats
No vendor lock-in
No hidden constraints
Just text.
Everything is Text
At the core of it all is a very simple idea:
Everything is just text.
- Your notes → text
- Your tasks → text
- Your configuration → text
- Your system → text
The system doesn’t need to “understand” your data in a proprietary way.
It just needs to orchestrate it.
That’s the shift.
Not from one app to another…
…but from apps → systems
Enter TextRoots
TextRoots comes from that exact realization.
Not as “another editor”
—but as something closer to a:
Personal Content Operating System
A system where:
- content is modular
- storage is interchangeable
- interfaces are flexible
- and everything flows through simple text
Where you can:
- edit locally
- sync globally
- switch interfaces
- compose your own workflows
And most importantly:
You own your data. Completely.
Closing Thought
Looking back, the journey makes sense:
- Evernote showed the convenience
- The CLI showed the simplicity
- Emacs showed the power
But none of them combined all three.
That’s the gap TextRoots is trying to fill.
Not by replacing everything…
…but by sitting underneath it all.
Quietly.
As the system that lets you finally feel like:
your thoughts are truly yours again.