> Right now, all these plain text strings are stored in a SQLite database locally on your computer. But we have plans to remove the reliance on a custom database and to store all notes as simple .txt files inside a folder.
I'm curious why would you want to move away from SQLite?
1. File versioning
2. Easier self-hosted syncing
3. Better data portability (although we already support exporting to .txt)
I would love to hear counterpoints. Currently, SQLite works pretty well, and our custom database is pretty simple (plus, our database code is also open source[1]).
[1] https://github.com/nuttyartist/notes/blob/master/src/dbmanag....
I have experience with flat file CMS systems (similar usecase) and at some point of complexity you end up rewriting your own database. Once every file has UUID an you have text file indexes of these than you realize you might have gone too far.
But not all projects need that and the argument for version control is big.
An encrypted DB will be a differentiator compared to every other offline editor (Joplin et al). It would also appeal to privacy-conscious enterprise users whose laptops may get automatically backed up.
You can support a timed export to text files for those other use-cases.