a large appeal of making your PKM Markdown-based is that you get data portability and compatibility with multiple tools. don’t dismiss Logseq, but do know it’s more limited than other Markdown PKMs on this angle.
i have an ancient PKM that i used to edit with vim. recently i installed Obsidian, Dendron, Logseq and a few others and just hopped between these daily to manage that PKM instead. Logseq’s journalling and time-tracking is a beauty, but you can’t use it on a PKM worked on by other tools without it stripping every blank line from your Markdown files and converting every top-level item to a bullet point.
in the end i always return to Obsidian. it plays nicely in any multi-tool environment i’ve dreamt up: it’s super easy to switch to, and a decade from now should i have a reason to, away from.
i have an ancient PKM that i used to edit with vim. recently i installed Obsidian, Dendron, Logseq and a few others and just hopped between these daily to manage that PKM instead. Logseq’s journalling and time-tracking is a beauty, but you can’t use it on a PKM worked on by other tools without it stripping every blank line from your Markdown files and converting every top-level item to a bullet point.
in the end i always return to Obsidian. it plays nicely in any multi-tool environment i’ve dreamt up: it’s super easy to switch to, and a decade from now should i have a reason to, away from.