> The way it worked was that they stored new/existing notes in an SQLite table with UUIDs. This of course makes it very difficult to use bash tools, other IDEs, etc. to work with your notes after Joplin has ingested them.
This is the real deal breaker for me for evaluating any note-taking tool.
If the Obsidian app dies tomorrow, my notes will be fine.
If Joplin gets abandoned, then I will have to deal with all the imports/exports into a new tool.
Bash tools are really powerful.
One can even take a git (not just GitHub) backup of one's Obsidian notes easily.
With binary files like SQLite, the git backups work, but they don't provide a meaningful diff.
Joplin can export all of your notes as markdown right now using the export feature. It is not how Joplin works with it internally, but if it did shut down tomorrow, all of your notes can still be exported as plain text markdown into another editor, such as Obsidian.
This is the real deal breaker for me for evaluating any note-taking tool.
If the Obsidian app dies tomorrow, my notes will be fine.
If Joplin gets abandoned, then I will have to deal with all the imports/exports into a new tool.
Bash tools are really powerful.
One can even take a git (not just GitHub) backup of one's Obsidian notes easily.
With binary files like SQLite, the git backups work, but they don't provide a meaningful diff.