Block content is supposed to be updated often and that would break the reference by title that you want. Currently when you update a page title, all references to it are updated. Of course we can’t do this with block content since it’s updated so often. This is why blocks have IDs to reference them.
I can’t disagree more. Apple does this with iOS by hiding the file system and now we have children that have no idea of what a file is. It’s important to keep the user aware of the file system because it’s a very powerful way to manage data independently from the application. Logseq does already a great work by reflecting its data structure (pages, blocks etc) into Markdown files.
It’s about locking users into their product. Since Logseq edits Markdown files live on the user file system, Logseq is a tool before being a product and you can’t beat standards like files and Markdown syntax with a proprietary online service.
Your concerns are more about UI/UX than Logseq’s data structure and storing mechanism.
You can’t expect such fundamental chances in Logseq at this point… on the other hand, I discussed this query builder mockup two days ago with Logseq UX designer, since it could be the next focus once whiteboards and sync are ready: