2 ms·
Why is that a problem if you are already going to be using specific software to interface with your notes don't you want it stored in an optimized foolproof for
by thingortwo 5mo ago
Why is that a problem if you are already going to be using specific software to interface with your notes don't you want it stored in an optimized foolproof format that is also one the preferred format recommended by library of congress?
And if you want always direct edit access and do it often why not then a simple plain text since either way you will be dependent on the software if you like the additional features it offers which aren't inside .md like linking and other
- Macha 5mo agoYou can use standard markdown links in obsidian, and even wikilinks are often supported (e.g. pulldown-cmark supports them). Or you can configure obsidian to prefer standard markdown links (https://obsidian.md/help/settings#Use%20Wikilinks https://obsidian.md/help/settings#Use%20Wikilinks) My notes were _already_ a folder of markdown, so I pretty seamlessly moved from VS Code as my notes app to obsidian and could move back to a text editor if obsidian turns evil. This might be part of why I’m less enthusiastic about their canvas thing, but then I was never a mind map or scrap board person anyway.
- chr15m 5mo agoYes it's often a problem. I am a Joplin user. Many times I have thought "X would be so much easier if these were just Markdown files on disk." Joplin has an API you can use, but it's annoying. Files on disk would be better. > if you want always direct edit access and do it often why not then a simple plain text I like the Joplin UI and features. I also have use-cases where I want plain text access outside Joplin. Obsidian shows its possible to have both (but I also want software libre).