I was originally also a pretty big anti-fan of the whole db idea. But it makes sense here. What I want is a block-oriented outliner with a lot of referencing a

I was originally also a pretty big anti-fan of the whole db idea. But it makes sense here. What I want is a block-oriented outliner with a lot of referencing around. This is not a great use-case for raw files (the referencing everywhere, specifically), while it's a pretty trivial one for let's say SQLite (which they're using here). Do note that I believe the current plan is to have two-way sync between files and the db, so presumably custom modification of md files should still work fine. But we'll see how that evolves. This is exacerbated by e.g. block IDs, which right now have to be shoehorned into the markdown format, while being hidden by the editor - which can be error prone as those IDs can move around. With a DB that's a solved problem. In Obsidian when you're doing block-level linking you end up with explicit "^jnflds" ID markers all over the place at line ends, which is quite awful if that's your primary use-case (to be clear, Obsidian overall is great, just not what I'm looking for - but if you care about the "raw files" approach, they seem to be embracing it).