4 ms·

If you don't need the extensive extension library of obsidian and want an open source tool, I would advise for Joplin. Tthe philosophy of logseq is completely d

If you don't need the extensive extension library of obsidian and want an open source tool, I would advise for Joplin. Tthe philosophy of logseq is completely different of obsidian (and joplin), being centered on lists instead of documents

keep320909 3y ago
Logseq is journaling app with graphs. Notes are not organized in folders, but tags. I find journaling much better. I never procrastinate deciding into what category/folder/doc notes should fit. I just put everything into journal and fluently refactor as time goes.
- kirso 3y ago
  +1 and if you need to replicate some structure you can use namespaces like review/weekly
- aprdm 3y ago
  Can you expand how you refactor ?
  - keep320909 3y ago
    Take bullet point, and move it to new page. Or extract all mentions of tag into single page. There are some basic hotkeys and commands. Refactoring is perhaps strong word, more like mouse dragging and copy&paste. It just feels like refactoring code. I can move things around without worrying something disappears or gets forgotten. I can also leave things half finished, without negative effects on readability and discoverability.
jauntywundrkind 3y ago
Joplin having data in a db is a non-starter for me. The flat-file nature of Logseq makes it much easier for me to script/mine/garden my digital garden.
- aprdm 3y ago
  Hm really ? It easily exports to markdown, and scripting against sqlite is very straightforward too
  - jauntywundrkind 3y ago
    The impedance feels unnecessary. I want my data checked into git, and directly accessible. I don't feel like custom schemas and database drivers, as a user, do anything but make the operational loop painful. I can quickly use any mdast library/toolkits and some terrible shell scripts to make anything possible in moments.
    - aprdm 3y ago
      I guess it depends the person, dealing with sqlite + python doesn't need dependencies or custom drivers and is easy to do/easier to manage for me than bash scripts
      - jauntywundrkind 3y ago
        The tools to manipulate SQL aren't that bad, no. But rather than having a self explanatory markdown & flat file, now I have to start learning about the schema & making specific tools (in my preferred language) for manipulating Joplin's schema. Suddenly I'm digging through 20 different technic specs to decode what data is where, how it works, and what I can do to it. Want to edit history? This is the best help you'll get, pray it's adequately technical to expedite you to your purpose: https://github.com/laurent22/joplin/blob/dev/readme/dev/spec/history.md https://github.com/laurent22/joplin/blob/dev/readme/dev/spec... As I began with, I struggle to imagine anything that generates anywhere near as much user agency as flat files and markdown. Having boring common data & systems lets me apply portable skills I already have, rather than having to skill up in some particular product's own ecosystem.

keep320909 3y ago

Logseq is journaling app with graphs. Notes are not organized in folders, but tags. I find journaling much better. I never procrastinate deciding into what category/folder/doc notes should fit. I just put everything into journal and fluently refactor as time goes.

kirso 3y ago
+1 and if you need to replicate some structure you can use namespaces like review/weekly
aprdm 3y ago
Can you expand how you refactor ?
- keep320909 3y ago
  Take bullet point, and move it to new page. Or extract all mentions of tag into single page. There are some basic hotkeys and commands. Refactoring is perhaps strong word, more like mouse dragging and copy&paste. It just feels like refactoring code. I can move things around without worrying something disappears or gets forgotten. I can also leave things half finished, without negative effects on readability and discoverability.

jauntywundrkind 3y ago

Joplin having data in a db is a non-starter for me. The flat-file nature of Logseq makes it much easier for me to script/mine/garden my digital garden.

aprdm 3y ago
Hm really ? It easily exports to markdown, and scripting against sqlite is very straightforward too
- jauntywundrkind 3y ago
  The impedance feels unnecessary. I want my data checked into git, and directly accessible. I don't feel like custom schemas and database drivers, as a user, do anything but make the operational loop painful. I can quickly use any mdast library/toolkits and some terrible shell scripts to make anything possible in moments.
  - aprdm 3y ago
    I guess it depends the person, dealing with sqlite + python doesn't need dependencies or custom drivers and is easy to do/easier to manage for me than bash scripts
    - jauntywundrkind 3y ago
      The tools to manipulate SQL aren't that bad, no. But rather than having a self explanatory markdown & flat file, now I have to start learning about the schema & making specific tools (in my preferred language) for manipulating Joplin's schema. Suddenly I'm digging through 20 different technic specs to decode what data is where, how it works, and what I can do to it. Want to edit history? This is the best help you'll get, pray it's adequately technical to expedite you to your purpose: https://github.com/laurent22/joplin/blob/dev/readme/dev/spec/history.md https://github.com/laurent22/joplin/blob/dev/readme/dev/spec... As I began with, I struggle to imagine anything that generates anywhere near as much user agency as flat files and markdown. Having boring common data & systems lets me apply portable skills I already have, rather than having to skill up in some particular product's own ecosystem.