qlyoung's wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
note_taking_programs [2025/02/15 19:44] – created qlyoungnote_taking_programs [2025/08/21 15:35] (current) – add mention of bases qlyoung
Line 7: Line 7:
 === Notion === === Notion ===
  
-Offline: No +  - Offline: No 
-Editor implementation: Web/Electron +  Editor implementation: Web/Electron 
-Mobile exp: ★★☆☆☆ +  Mobile exp: ★★☆☆☆ 
-Sync: N/A +  Sync: N/A 
-Org: Hierarchical+  Org: Hierarchical
  
 I used to use [[https://www.notion.so|Notion]]. Notion is organized around the idea of content blocks. Each block has a type; text, image, database etc. I used to use [[https://www.notion.so|Notion]]. Notion is organized around the idea of content blocks. Each block has a type; text, image, database etc.
Line 26: Line 26:
 === logseq === === logseq ===
  
-Offline: Yes +  - Offline: Yes 
-Editor implementation: Web/Electron +  Editor implementation: Web/Electron 
-Mobile exp: N/A +  Mobile exp: N/A 
-Sync: Yes +  Sync: Yes 
-Org: Sequential+  Org: Sequential
  
 Logseq is interesting. It's an outliner with a unique model for note taking. It's organized around the idea of a sequence of logs. The happy path for logseq is that each day you open up today's daily note, write whatever it is you are working on or thinking of, and attach identifiers to blocks of content. Later on, if you want to extend the notes you took on that content, you're supposed to synthesize a new note in today's journal page by transcluding the content you already wrote via its identifier. Then there's some hand wavey idea that "later" you'll pull all of those blocks into their own topic pages. Logseq is interesting. It's an outliner with a unique model for note taking. It's organized around the idea of a sequence of logs. The happy path for logseq is that each day you open up today's daily note, write whatever it is you are working on or thinking of, and attach identifiers to blocks of content. Later on, if you want to extend the notes you took on that content, you're supposed to synthesize a new note in today's journal page by transcluding the content you already wrote via its identifier. Then there's some hand wavey idea that "later" you'll pull all of those blocks into their own topic pages.
Line 40: Line 40:
 === Obsidian === === Obsidian ===
  
-Offline: Yes +  - Offline: Yes 
-Editor implementation: Web/Electron +  Editor implementation: Web/Electron 
-Mobile exp: ★★☆☆☆ +  Mobile exp: ★★☆☆☆ 
-Sync: Yes +  Sync: Yes 
-Org: Hierarchical+  Org: Hierarchical
  
 Currently I use [[https://obsidian.md|Obsidian]]. Obsidian is fundamentally a markdown editor. Then it has a whole host of plugins that add rich presentation and other capabilities into the markdown editor. Currently I use [[https://obsidian.md|Obsidian]]. Obsidian is fundamentally a markdown editor. Then it has a whole host of plugins that add rich presentation and other capabilities into the markdown editor.
Line 53: Line 53:
  
 On the other hand, Obsidian wants to have its cake and eat it too. It wants to get all the advantages of Markdown but also offer high level functionality such as task tracking, tabular data storage, query languages etc. To make these work well, the underlying data really wants to be structured. But there is no structured data store in Obsidian, the data format is "just Markdown". How to solve this conundrum? Most of the value-added features do so by storing structured data **in Markdown**. This is such an obviously bad idea and the results are as bad as you might expect. You end up with a bunch of shitty home grown databases whose disk format is an insane extension of Markdown. Now it's no longer easy to exit the ecosystem, you cannot get at your data without the Obsidian code necessary to render it, etc. On the other hand, Obsidian wants to have its cake and eat it too. It wants to get all the advantages of Markdown but also offer high level functionality such as task tracking, tabular data storage, query languages etc. To make these work well, the underlying data really wants to be structured. But there is no structured data store in Obsidian, the data format is "just Markdown". How to solve this conundrum? Most of the value-added features do so by storing structured data **in Markdown**. This is such an obviously bad idea and the results are as bad as you might expect. You end up with a bunch of shitty home grown databases whose disk format is an insane extension of Markdown. Now it's no longer easy to exit the ecosystem, you cannot get at your data without the Obsidian code necessary to render it, etc.
 +
 +Edit: I originally wrote the above paragraph in 2024. It's now late 2025 and I have been vindicated. https://help.obsidian.md/bases/syntax
  
 Consequently I don't use any of the plugins in Obsidian that do this and so for me, most of the advanced workflows are lost on me and it ends up as a glorified Markdown editor. However, the editor itself is quite nice so it's still worthwhile to use it vs e.g. vim on a directory tree. The sync service (which costs money) works well and does a good job syncing apps between my various computers and phone. The mobile editor is not great but as it is an App it's more functional than alternatives. Writing Markdown is fine when you have a full keyboard but it's not a good experience on mobile. Consequently I don't use any of the plugins in Obsidian that do this and so for me, most of the advanced workflows are lost on me and it ends up as a glorified Markdown editor. However, the editor itself is quite nice so it's still worthwhile to use it vs e.g. vim on a directory tree. The sync service (which costs money) works well and does a good job syncing apps between my various computers and phone. The mobile editor is not great but as it is an App it's more functional than alternatives. Writing Markdown is fine when you have a full keyboard but it's not a good experience on mobile.
Panorama theme by desbest
note_taking_programs.1739648695.txt.gz · Last modified: by qlyoung
CC Attribution-Noncommercial-Share Alike 4.0 International Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International