Yes, that’s what I meant saying that it narrows down outside-logseq usage to devs, compared to Markdown. There are some ways to use it for laymen also but they are very niche and the tools are not at all as mainstream as Markdown editors.
For one, I would be interested to publish SQLite to a webpage like I do now for Markdown with Hugo. Also I am interested in having a way for an LLM to interact with an SQLite database in a RAG paradigm. I would like this also from within Logseq but also from outside, for both future-proofing and functionality - maybe a voice-based way to “discuss” with the database.
All in all, SQLite seems like a good idea, I just need to see what and how it stores the data inside so querry results are useful if done from outside…