5 ms·
Yep, good reasons to use Logseq. I picked Obsidian over Logseq because of the larger community, and because I thought the former's UI looked suitable for hierar
by creamyhorror 3y ago
Yep, good reasons to use Logseq. I picked Obsidian over Logseq because of the larger community, and because I thought the former's UI looked suitable for hierarchical notes in main categories, which is my usual approach. I go to the right folder and append to the end of the relevant note. I do like Logseq's more free-flowing, block-tagging, hypertext-journal approach, but thought I didn't really need the journal format for now.
If Logseq can also do hierarchical organising/browsing with a simple sidebar interface, I think I'll give it a go. Does it work well for that use case? What's nice is that you can run both Logseq and Obsidian on the same Markdown files, since they're (mostly compatible) Markdown, so I'm not too worried about switching as needed or even using both.
- eitland 3y agoI'm not aware of any extension that gives you a hierarchical sidebar on the left. The right side however has a built in "Contents" page - which tells you what it is for - only as far as I know one has to fill it out oneselves. That said, my goal was not to convert you or anyone. I am a NetBeans user myself so I know a bit or two about others telling me why I should switch to "clearly superior alternatives" and I don't want to do that to others ;-)
- creamyhorror 3y agoHah, appreciate it. Although I actually do like finding out about better alternatives and weigh the benefits of switching. It's good to know what people are happy about, even if it isn't quite for oneself. Sounds like Obsidian fits me better than Logseq for now (for the inherent hierarchical organisation). Though one of these days I'll try running Logseq on the same files just for a different view and to try out journalling.
- eitland 3y agoYou maybe already know, but I write it anyway in case you or someone else find it interesting: AFAIK Logseq docs encourage new users to put everything under Journal and just tag the relevant blocks. Multiple hierarchical tags are possible, as are aliases, which comes in handy, e.g. I have examples of good ux nested three steps down from root, but in practice I write [[Good UX]] and paste the screenshot and I am done, it shows up at the right place, but is a lot more readable in my journal. BTW, that alias could have been #GoodUX as well and I would have gotten away with hashtag notation.)