Gregory's Server
@yuliyan @kepano @obsidian not really: the canvas format is pretty clear JSON, so translating it is easy. If/when #obsidian goes bad the install base is big enough that tools to translate to whatever replaces it will be available. Dataview is the biggest problem and I believe there’s a stand-alone version of that in the offing.
|
2 comments
 @Colman @kepano @obsidian I believe many things that Dataview does can be done by improving the core search functionality. When it comes to search, I. believe that computers in 50 years should easily be able to display search results based on human language queries. Data should be observable but does it need a technical database implementation other than search indexing? |
@Colman @kepano @obsidian I meant "amazing" as in realizing that the canvas JSON is already pretty resilient. Thank you for clarifying.
Regarding Dataview, I am not in the school of thought, that wants to see Obsidian have more database functionality that it does right now. The referencing between notes and folder structure enforce simplicity and resilience. Combined with tags and naming conventions it is already pretty powerful without dependency cost.