The user interface change I was suggesting would have zero impact on interoperability.
Given the description you provided earlier:
- User creates a new “note”.
- Obsidian creates a new system folder with the same name.
- Each note can have child “notes”.
3a) Each note has a “parent”, which is either root or another note.
3b) Each note can have “children”, which are new notes: see #1, above.
I disagree with your interoperability comment.
If every new note ends up as a new folder, the underlying folder structure becomes horrendous to use with any other system that doesn’t hide the folders.
I use folders a lot with Obsidian even though I don’t necessarily need them in Obsidian but I know from past experience that tools come and go, nothing lasts forever. So there will be time when I need to switch to something else and I want my filesystem structure to be clean and well structured so that in a pinch, I can use any text or code editor and still be able to navigate my notes based on those folders.
Technically, one could claim this doesn’t “break interoperability” but at least for me, usability is part of that interoperability and this would break it for me, making the underlying structure near unusable outside/after Obsidian.