![]() > Installing multiple task plugins shows that something is "broke" on the user side. Coincidentally, this seems also one of the reasons why Joplin is using a database. And the reason for all this is also because markdown is lacking definitions for what obsidian-people are doing with it. So some features of your parts might break when switching away from Obsidian. The thing is, technically you are not even having proper markdown, but a fork with some extensions of Obsidian. > And even if It's like that, my markdown files would survive everything I've tested enough plugins over the years to know their dark corners. And even worse if you are not realizing the errors early. That's useless when the app itself is not working. > and b) easy to fix since it's a text file. Coincidental, the Obsidian-devs are also working on that front, but nothing is finished yet. Datacore, the next project of the Dataview is supposed to bring this, but it's not even usable yet AFAIK. Dataview is really just an elaborated search, there is no good level of interaction. Good for you, but that is very low level in terms of data-handling. ![]() Maybe not for you, when you lack the knowledge, but markdown is similar closed for anyone not understanding filesystems and editors. Joplin is using a popular open database with a healthy community and good tooling. > by separating that in their DB, it's a big NO for me since it's a closed silo. The way it's handled can make the difference in control.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |