Earlier quoted context omitted.
Yes, but the average Obsidian user may or may not know what a database is an why they should care. As an engineer I like precise language, but we should not forget that multiple audiences require multiple levels of explainations. Otherwise it is a bit like saying "all monads are functors" when trying to make your reader care for investing time and energy into understanding the concept of monads. The problem there of…
> Yes, but the average Obsidian user may or may not know what a database You can't constantly optimize your communication for the least educated recipient. Obsidian is full of technical, specialized terms. If you don't know a word, research it. And database as a concept is common knowledge today. Everyone will have the word heard in news at least, most will have a rough understanding of its purpose. And people using…
However, it isn't exactly rocket science and if one developes such a feature it makes sense to test it with multiple realistic usecases anyways, so why not just use those to show the users how it can be used?
Unless ofc a feature is developed in mental isolation by a recluse with a niche interest in the code without thinking about the potential use at all. But then it is probably more like a extracagant hobby than a serious project that others should rely on.