Saying Obsidian uses just TXT files suggest, that I could use any editor and that Obsidians file format is compatible with any editor.
That is technically the truth, but the problem is, that if I decide to use another editor I might get problems because of the lacking ability to usefully edit the metadata.
So, if I use Obsidian, the files are de facto not compatible with other editors.
Of course I could switch off of Obsidian and I have the raw data, so I am not locked in. But I think stating that obsidan uses just txt files without any explanation is a bit misleading.
Obsidian is just another WYSIWYG Editor.
What makes it a problwm is the MD-dialect they employ.
For example callouts in obsidian are not possible in the markdown flavor of vs-code.
I can’t do thiy in vscode
> [!warning]-
> This is a collapsed warning
But that is what I quite like and I found no other programs which handles as well as Obsidian.
Maybe some parts of vscode markdown with plugins closes the gap.
So? It’s stored in the same folder locally
Saying Obsidian uses just TXT files suggest, that I could use any editor and that Obsidians file format is compatible with any editor. That is technically the truth, but the problem is, that if I decide to use another editor I might get problems because of the lacking ability to usefully edit the metadata. So, if I use Obsidian, the files are de facto not compatible with other editors.
Of course I could switch off of Obsidian and I have the raw data, so I am not locked in. But I think stating that obsidan uses just txt files without any explanation is a bit misleading.
Obsidian is just another WYSIWYG Editor.
What makes it a problwm is the MD-dialect they employ.
For example callouts in obsidian are not possible in the markdown flavor of vs-code.
I can’t do thiy in vscode
> [!warning]- > This is a collapsed warningBut that is what I quite like and I found no other programs which handles as well as Obsidian.
Maybe some parts of vscode markdown with plugins closes the gap.