Thread by @abialbonpaul

#PKM beginners looking for completely free digital solutions often come to a decision to make between the amazing @obsdmd and the soon catching up open-source solution @logseq.

I scoured the internet to read through multiple users opinions and here are my biased thoughts:

To most, @obsdmd is a clear winner.

It's
- Free
- More mature software
- Has more plugins
- Has a larger community
- Is faster in processing large notes
- Better graph view
- Has a pricey but good publish option

But there are few (like me) who find at home in @logseq

The key difference in @logseq is this:
The smallest unit of a note (an atomic note) is a bullet point or a block.

It is an outliner at its core. Each block can have properties, tags or reference a new page.

And this opens some amazing use-cases!

On the other hand, in @obsdmd, the atomic note is a file.
Though you can reference single blocks and tag them, Obsidian does not understand block references intuitively.

You can also arrange these files in different folders.

You can record details of all calls made in the daily note in @logseq. Each block is tagged with a call tag and name. Later references to all calls made with details to call can be seen

There are numerous uses cases and you do not need to worry about where you put down the note

While this is possible in @obsdmd, the reference backlink shows a bit of context from the note where the reference originated.

But since Obsidian does not understand blocks separately, only some context is shown in the reference backlink.

In @logseq, there are no folders. You can write wherever you want, Either in the daily note or in a new page. Since you do not have to create a new file for every new idea, there's a seamless flow to ideas.

In @Logseq, the only decision to make is:
Should you start a new sibling block or child block?
A sibling block is the start of a new idea while a child block enumerates the parent block's idea.

I am so thrilled about Logseq and I am going to dedicate my time to learn more about #PKM, @logseq and better ways to organise our brains 🧠
Follow me to be a part of that journey!
Thank you for reading.