4 ms·
What I am wondering about is that although the basic files are markdown, some of the plugins might be proprietary. So that the part of the contents in the markd
by arnejenssen 3y ago
What I am wondering about is that although the basic files are markdown, some of the plugins might be proprietary. So that the part of the contents in the markdown files in effect creates a lock-in?
- brightball 3y agoPotentially. I don't use many of the plugins so I can't say with authority.
- AJ007 3y agoI would suggest editing and reading the markdown files in other editors to make avoid getting "locked in." You certainly could create your own lock-in by making some unique workflow that requires a combination of plug-ins to function. The plugins are all third party, some of them are just annotating the existing markdown files, some are just visual.
- swozey 3y agoSo you only use Obsidian for its vaults/syncing?
- theshrike79 3y agoMy workflow isn't reliant on Obsidian's plugins, they just make stuff easier. Like having a template for my Daily Note that also automatically includes all files tagged #todo using Data View. Or a few global shortcuts via Keyboard Maestro that open specific notes on Obsidian. I could maybe whip up a similar system in a day on top of any editor that can render Markdown and handle links, but now I don't need to.
- georgejfrick 3y agoNo, becasue the plugins are just JavaScript running against markdown that generally produce more markdown. You might get a plugin that produces an image and that would "stop working"; but it hard for the JS to be locked down/etc.