File over app
stephango.com
If you want to create digital artifacts that last, they must be files you can control, in formats that are easy to retrieve and read. Use tools that give you...

I personally wouldn’t recommend obsidian (mentioned at the end of the article), but still, I think the article is worth reading.

  • @[email protected]English
    5•10 months ago

    I wonder this with obsidian also, it is one of the things that keeps me from diving in head first.

    It seems a lot of its “powerful” functions are against it’s plain text advantage. However I don’t really see an easy way around it.

    At least at the end of the day you or someone else could write a script to modify the plain text files for the next app.

    • @brenticusEnglish
      6•10 months ago

      It’s tricky for sure. The plain text is great, and all the functionality is built off of plain text (even the canvas!), but replicating the functionality isn’t trivial by any stretch of the imagination. Migration is easier because of the text files, but will it be as easy to see the links between notes? Or query all the notes I need more detail in? Or map it all out visually?

      I think reimplementing the core obsidian functionality in a FOSS clone would be fun… except I already have a queue of projects and not a lot of time, so here I am complaining instead 🤷

        • @brenticusEnglish
          1•10 months ago

          Logseq is a great alternative. It’s very much not a clone, though. It has a different paradigm on how it views notes and the functionality isn’t exactly 1:1.

    • @[email protected]English
      5•10 months ago

      Try logseq, it’s foss and solves some of these problems. Mostly compatible with files from obsidian