ⲃⲩⲣⲕⲅⲣⲁⲩⲓⲩⲥ 🜨 on Nostr: I think I have a winner in my #Logseq vs #Obsidian notetaking battle. Despite me ...
I think I have a winner in my #Logseq vs #Obsidian notetaking battle.
Despite me WANTING to prefer Logseq to Obsidian based on its #OpenSource nature, but I simply cant. Obsidian functions in a way much more natural to me.
I don't use these tools strictly for #PKM but also for personal #ProjectManagement, keeping a documented archive of personal files (identity documents, medical information, etc) and Logseq's lack of folders, combined with the fact that it renames attachments (assets), is a dealbreaker. Obsidian helps me maintain a working structure (e.g. I can archive files as generic or as specific as I want, while being able to reference them elsewhere as needed - for example, I can keep a generic attachments folder for #zettelkasten related images, PDFs, while having categorized documents elsewhere).
Also, I simply don't find myself using blocks and #block #properties as much. My main use case here have been #work #meetings, but except removing some friction on starting to type, I can substitute that with creating a templated page.
It really, really frustrates me that Obsidian is #closedSource, but still, I consider that it gives me more #freedom - it respects MY structure, the underlying files, and is, in essence, a powerful #Markdown editor. Logseq is not. It uses Markdown as a base, but is in essence an outliner of its own kind. It has its usecases, but Obsidian seems to be overall more flexible, more powerful, and ironically, more future-proof.
Despite me WANTING to prefer Logseq to Obsidian based on its #OpenSource nature, but I simply cant. Obsidian functions in a way much more natural to me.
I don't use these tools strictly for #PKM but also for personal #ProjectManagement, keeping a documented archive of personal files (identity documents, medical information, etc) and Logseq's lack of folders, combined with the fact that it renames attachments (assets), is a dealbreaker. Obsidian helps me maintain a working structure (e.g. I can archive files as generic or as specific as I want, while being able to reference them elsewhere as needed - for example, I can keep a generic attachments folder for #zettelkasten related images, PDFs, while having categorized documents elsewhere).
Also, I simply don't find myself using blocks and #block #properties as much. My main use case here have been #work #meetings, but except removing some friction on starting to type, I can substitute that with creating a templated page.
It really, really frustrates me that Obsidian is #closedSource, but still, I consider that it gives me more #freedom - it respects MY structure, the underlying files, and is, in essence, a powerful #Markdown editor. Logseq is not. It uses Markdown as a base, but is in essence an outliner of its own kind. It has its usecases, but Obsidian seems to be overall more flexible, more powerful, and ironically, more future-proof.