Logseq - A Powerful Tool for Thought
Logseq is a hidden gem in the Tools for Thought space. In this article we explore what is Logseq, its strengths and how you can get started with Logseq.
This article has been moved over to Medium, follow this link to read it.
I am diving in, and have journals, assets and pages indexed from Logseq into Devonthink3 (as I have a similar setup for Obsidian) and definitely find Logseq more compatible with my outlining habits acquired over the years. I have added a few plugins (agenda, tabs, tags, bullet threading) and these add just enough extra to make me feel like I can do what needs to be done here. I doubt I would have made this effort without the timely encouragement from TFTHacker's post.
Comparing Logseq and Obsidian to Notion, things I miss:
Ease of Table use - Logseq has Luckysheet (great, but I don't know how to integrate it). Obsidian has MD table editors and I saw a plugin for Notion-like tables, but hadn't used it for now.
Columns for text - In Logseq I could only do this by kanbans. In Obsidian a plugin made it a "view" feature, not really 2 separate text columns as in Notion.
Both are very into queries for requesting and visualizing data, I suppose, and I'm still starting to learn it. I got kinda lost with the abundance of Obsidian's plugins. This gave Logseq an easier learning curve for me. But Obsidian sure appears to have more features, a bigger community and growth.
The reason I'm using Logseq is its built-in PDF handling, with its linked annotations and reading. Obsidian has an Annotation plugin which I couldn't use, and its other option for annotation is a paid feature in a plugin.
Of course I may be missing a lot. But so far so good, compared to when I didn't use any of them.