I feel you. I've tried so many things too.
Obsidian just came "too late" in this journey of trying things out. I had already somehow settled with Vimwiki. I briefly tried Obsidian, but I am somehow at a point now where I don't want to learn a new tool. What I have now just works. Vim is an extension of my thoughts. I get frustrated when I see a colleague or student trying to navigate a file with his mouse. But they get frustrated too when I give a hands-on tutorial and they can't follow what I'm doing on the screen.
The proper method is the one that just works, no questions
The table of contents in obsidian solved a long time ordeal of navigating long documents by endless scrolling and wishing you remembered where that specific subject was. Now it's a quick scroll on the right, click, bum. And if that doesn't work right away, it means the document is messy, so I proceed to refactor and indeed that solves the problem and makes the document better. I can't believe this workflow isn't more common among text editors.
I tried vimwiky but it was way too packed and with time I realized I needed something barely above a txt. For a time that's what I did until I got to know markdown.
But anyway, the definitive answer is the one you said: "What I have now just works". Period.
reply
To be fair, I barely use the wiki part of it. It's mostly one central text file, from which I sometimes branch out to a separate file using [[other page]]. The searching to find something I wrote months agao happens mostly on the main file using vim's /. I'm not really using it much as a Zettelkast.
reply
Obsidian allows to use wiki links natively, but I found out that I never use them in practice. I do refer in the documents to other files by name, but I found out that if you keep a proper structure, even for very long projects, you will hardly need wiki links, and if you ever do, chances are you are doing things wrong. Unless you are making an actual wiki, but that's at company-level, can't be at personal level.
reply