I was so impressed by logseq……until I realized my files are all managed in a database. Obsidian just saves your notes as basic markdown files. That ended up being a big enough reason to go back.
If that’s not a big deal to you, absolutely logseq 100%.
Same. I don’t like Joplin for the same reason. I mean, the encryption feature is super good and all, but if I can’t edit my notes in any app I want whenever I want, then it’s a no-go for me.
It was the same for me. I stopped looking at Logseq the second I saw that it didn’t simply save text files. It shouldn’t really be an issue since Logseq is open source so you won’t lose access to your files but for notes I like the simplicity of plain text files for backup in git, for sharing and for searchability.
Yep same reason here. I use git for backup and sync, if my notes are in a db I can’t easily do that.
In addition to those benefits, I’d like for my information to outlive the tool I’m using to manage it, which is less likely when using something db-centric.
Logseq is better than obsidian and it’s not even at version 1 yet
I was so impressed by logseq……until I realized my files are all managed in a database. Obsidian just saves your notes as basic markdown files. That ended up being a big enough reason to go back.
If that’s not a big deal to you, absolutely logseq 100%.
Same. I don’t like Joplin for the same reason. I mean, the encryption feature is super good and all, but if I can’t edit my notes in any app I want whenever I want, then it’s a no-go for me.
It was the same for me. I stopped looking at Logseq the second I saw that it didn’t simply save text files. It shouldn’t really be an issue since Logseq is open source so you won’t lose access to your files but for notes I like the simplicity of plain text files for backup in git, for sharing and for searchability.
Yep same reason here. I use git for backup and sync, if my notes are in a db I can’t easily do that.
In addition to those benefits, I’d like for my information to outlive the tool I’m using to manage it, which is less likely when using something db-centric.