Obsidian is great; I was a happy user for a couple years. But I recently switched to Logseq and I think I’m already liking it more, and it’s because of something Logseq doesn’t do.
Obsidian lets you write a full markdown file, so step one is deciding how to write something down. Is it a nested list? Or a table? Or headings and subheadings with paragraphs?
In Logseq, everything is a nested list. This feels like a limitation, but I’ve been preferring it. The decision is made for you: you’re going to jot this information down as a list. So then you just start writing it.
People often tout that Logseq is open source, and while that is great, IMO there is also a design consideration that makes it better. Pretty much any kind of information you want to write down can be represented as a nested list. Doing it that way keeps everything simple, consistent, and more searchable. (Logseq’s built-in querying feature seems to be more powerful than Obsidian’s Dataview plugin, although I can’t say much about it since I haven’t really played with it yet.)
Both Obsidian and Logseq save (kinda) standard markdown files, so if you spend a lot of time in a plain text editor, you can still use that. You don’t lose anything by editing a file in a separate editor – they will both parse and re-index the file next time you view it in the respective app.
In Logseq, everything is a nested list. This feels like a limitation, but I’ve been preferring it. The decision is made for you: you’re going to jot this information down as a list. So then you just start writing it.
I really appreciate you posting this. I’m a long-time Obsidian user, and an Evernote user before that, and I never “got” Logseq. I just couldn’t understand what people saw in an app that didn’t let you “write” anything. I’ve tried to start using Logseq so many times and just given up because the interface made no sense.
Thanks to your comment I finally get it! I prefer to be using something open-source, so I’m going to give Logseq another go, now that I finally understand it, and see how that approach feels.
Obsidian is great; I was a happy user for a couple years. But I recently switched to Logseq and I think I’m already liking it more, and it’s because of something Logseq doesn’t do.
Obsidian lets you write a full markdown file, so step one is deciding how to write something down. Is it a nested list? Or a table? Or headings and subheadings with paragraphs?
In Logseq, everything is a nested list. This feels like a limitation, but I’ve been preferring it. The decision is made for you: you’re going to jot this information down as a list. So then you just start writing it.
People often tout that Logseq is open source, and while that is great, IMO there is also a design consideration that makes it better. Pretty much any kind of information you want to write down can be represented as a nested list. Doing it that way keeps everything simple, consistent, and more searchable. (Logseq’s built-in querying feature seems to be more powerful than Obsidian’s Dataview plugin, although I can’t say much about it since I haven’t really played with it yet.)
Both Obsidian and Logseq save (kinda) standard markdown files, so if you spend a lot of time in a plain text editor, you can still use that. You don’t lose anything by editing a file in a separate editor – they will both parse and re-index the file next time you view it in the respective app.
I really appreciate you posting this. I’m a long-time Obsidian user, and an Evernote user before that, and I never “got” Logseq. I just couldn’t understand what people saw in an app that didn’t let you “write” anything. I’ve tried to start using Logseq so many times and just given up because the interface made no sense.
Thanks to your comment I finally get it! I prefer to be using something open-source, so I’m going to give Logseq another go, now that I finally understand it, and see how that approach feels.