Question; So i'm also designing a "second brain" for myself/foss, and i've often had the debate of how much i should go with plaintext. On one hand it is nice

Question; So i'm also designing a "second brain" for myself/foss, and i've often had the debate of how much i should go with plaintext. On one hand it is nice for basic tools like grep, custom editors, easy backup, etc. However "lockin" is something i keep pausing on.. because for any advanced features you include, say spaced repetition over items in the document, becomes a unique DSL for your application most likely. Yea, it could be made from "just markdown" or w/e, but the functionality still only works in that one app. Eg i used some other Space Rep tool which advertised using just markdown, cool! But i can't port it anywhere, so yay it's plain text but the functionality still need to be refactored to work with other tools. This problem becomes more apparent when you add more complex features. Each unique/novel feature creates unique DSL to store state in "plaintext", which to me starts feeling like it destroys the core premise of plaintext. Thoughts on this issue?